Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

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.30% (FIRST EPSS).
  • Fixed version: Linux Linux 3360125d721c91d697c71201f18f042ff743e936, 6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7, 7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4.

Low priority for now. Upgrade to Linux Linux 3360125d721c91d697c71201f18f042ff743e936, 6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7, 7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4 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 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.

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 22th 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.3%

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-50760

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

    • 4.2affected
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before da7c78ea9e62bb65273d3ff19a3866ec205bfe18affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 3360125d721c91d697c71201f18f042ff743e936affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 981024abf5fe605c94d4f906f65d1b3408d628beaffected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 8f2d2badf8ca5e7e7c30d88840b695c8af7286f3affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 9d4057d0452243917e12eb19f1599c96f2f05b14affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before a8b54ad7106c0604c4adc4933138b3557739bce0affected · git
    • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before ca54639c7752edf1304d92ff4d0c049d4efc9ba0affected · git

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
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.293.14.12.14-122.293.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_77before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.293.14.12.14-122.293.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.293.14.12.14-122.293.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-50758Dec 24, 2025 · staging: vt6655: fix potential memory leak
    31Monitor
  • ← EarlierCVE-2022-50759Dec 24, 2025 · media: i2c: ov5648: Free V4L2 fwnode data on unbind
    0Monitor
  • Later →CVE-2022-50761Dec 24, 2025 · x86/xen: Fix memory leak in xen_init_lock_cpu()
    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 Linux3360125d721c91d697c71201f18f042ff743e936Vendor (CNA)
Linux Linux6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7Vendor (CNA)
Linux Linux7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4Vendor (CNA)
Linux Linux8f2d2badf8ca5e7e7c30d88840b695c8af7286f3Vendor (CNA)
Linux Linux981024abf5fe605c94d4f906f65d1b3408d628beVendor (CNA)
Linux Linux9d4057d0452243917e12eb19f1599c96f2f05b14Vendor (CNA)
Linux Linuxa8b54ad7106c0604c4adc4933138b3557739bce0Vendor (CNA)
Linux Linuxca54639c7752edf1304d92ff4d0c049d4efc9ba0Vendor (CNA)
Linux Linuxda7c78ea9e62bb65273d3ff19a3866ec205bfe18Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.293.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.293.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.293.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_771-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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 (8 more)

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

All records