Kernel resource leak via unreleased PCI reference
Published Dec 24, 2025 · Updated Dec 24, 2025
Reference-count leak in the amdgpu BIOS loader in Linux allows attackers to retain PCI device references during GPU initialization. When amdgpu_atrm_get_bios finds an ACPI ATRM handle and exits its PCI-device scan, it fails to call pci_dev_put on the retained pdev. The condition is limited to systems using the amdgpu on-platform ATRM BIOS path; published sources report a resource leak but no privilege gain, data access, or demonstrated crash.
Summary
What happened
Reference-count leak in the amdgpu BIOS loader in Linux allows attackers to retain PCI device references during GPU initialization. When amdgpu_atrm_get_bios finds an ACPI ATRM handle and exits its PCI-device scan, it fails to call pci_dev_put on the retained pdev. The condition is limited to systems using the amdgpu on-platform ATRM BIOS path; published sources report a resource leak but no privilege gain, data access, or demonstrated crash.
The record
- CVE
- CVE-2022-50760
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <3360125d721c91d697c71201f18f042ff743e936
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <6611feef35c0c8c4d297b28a7fc6ab3a2c47eca7
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <7c1ddf7c664b5bc91f14b1bdeaa45520ef1760e4
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <8f2d2badf8ca5e7e7c30d88840b695c8af7286f3
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <981024abf5fe605c94d4f906f65d1b3408d628be
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <9d4057d0452243917e12eb19f1599c96f2f05b14
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <a8b54ad7106c0604c4adc4933138b3557739bce0
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <ca54639c7752edf1304d92ff4d0c049d4efc9ba0
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <da7c78ea9e62bb65273d3ff19a3866ec205bfe18
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo