Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50760drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios()

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios() As comment of pci_get_class() says, it returns a pci_device with its refcount increased and decreased the refcount for the input parameter @from if it is not NULL. If we break the loop in amdgpu_atrm_get_bios() with 'pdev' not NULL, we need to call pci_dev_put() to decrease the refcount. Add the missing pci_dev_put() to avoid refcount leak.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.30% · top 77% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < da7c78ea9e62bb65273d3ff19a3866ec205bfe18
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 3360125d721c91d697c71201f18f042ff743e936
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 981024abf5fe605c94d4f906f65d1b3408d628be
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 8f2d2badf8ca5e7e7c30d88840b695c8af7286f3
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 9d4057d0452243917e12eb19f1599c96f2f05b14
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < a8b54ad7106c0604c4adc4933138b3557739bce0
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < ca54639c7752edf1304d92ff4d0c049d4efc9ba0
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50760 badge
[![CVE-2022-50760](https://cveledger.app/badge/CVE-2022-50760.svg)](https://cveledger.app/cve/CVE-2022-50760)

Record last updated .