Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50718: drm/amdgpu: fix pci device refcount leak

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Fixed version: Linux Linux 02105f0b3021ee5853b2fa50853c42f35fc01cfd, 3725a8f26bdbc38dfdf545836117f1e069277c91, b85e285e3d6352b02947fc1b72303673dfacb0aa.

Low priority for now. Upgrade to Linux Linux 02105f0b3021ee5853b2fa50853c42f35fc01cfd, 3725a8f26bdbc38dfdf545836117f1e069277c91, b85e285e3d6352b02947fc1b72303673dfacb0aa or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix pci device refcount leak As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So before returning from amdgpu_device_resume|suspend_display_audio(), pci_dev_put() is called to avoid refcount leak.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50718

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.8affected
    • 3f12acc8d6d4b2e62fab8f652d7075a859d80b42 and later · before 3725a8f26bdbc38dfdf545836117f1e069277c91affected · git
    • 3f12acc8d6d4b2e62fab8f652d7075a859d80b42 and later · before 02105f0b3021ee5853b2fa50853c42f35fc01cfdaffected · git
    • 3f12acc8d6d4b2e62fab8f652d7075a859d80b42 and later · before f13661b72a61708cecb06562f8acff068a4f31f7affected · git
    • 3f12acc8d6d4b2e62fab8f652d7075a859d80b42 and later · before d7352b410471cbebf6350b2990bae82bb0d59a76affected · git
    • 3f12acc8d6d4b2e62fab8f652d7075a859d80b42 and later · before b85e285e3d6352b02947fc1b72303673dfacb0aaaffected · git
    • before 5.8not affected · semver
    • 5.10.163 and later · up to and including 5.10.*not affected · semver
    • 5.15.86 and later · up to and including 5.15.*not affected · semver
    • 6.0.16 and later · up to and including 6.0.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50716Dec 24, 2025 · wifi: ar5523: Fix use-after-free on ar5523_cmd() timed out
    0Monitor
  • ← EarlierCVE-2022-50717Dec 24, 2025 · nvmet-tcp: add bounds check on Transfer Tag
    39Monitor
  • Later →CVE-2022-50720Dec 24, 2025 · x86/apic: Don't disable x2APIC if locked
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux02105f0b3021ee5853b2fa50853c42f35fc01cfdVendor (CNA)
Linux Linux3725a8f26bdbc38dfdf545836117f1e069277c91Vendor (CNA)
Linux Linuxb85e285e3d6352b02947fc1b72303673dfacb0aaVendor (CNA)
Linux Linuxd7352b410471cbebf6350b2990bae82bb0d59a76Vendor (CNA)
Linux Linuxf13661b72a61708cecb06562f8acff068a4f31f7Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records