drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios()
Noroxi assessment
Priority: Monitor (action score 22/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1079df6acf56f99d86b0081a38c84701412cc90e, 3.3, 3.5.
Low priority for now. Upgrade to Linux Linux 1079df6acf56f99d86b0081a38c84701412cc90e, 3.3, 3.5 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/radeon: Fix PCI device refcount leak in radeon_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 radeon_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.
- Published
- Oct 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1 and later · before 6.1.2
- linux linux kernel3.2.29 and later · before 3.3
- linux linux kernel3.2.60 and later · before 3.3
- linux linux kernel3.4.12 and later · before 3.5
- linux linux kernel3.5.5 and later · before 3.6
- linux linux kernel3.6.1 and later · before 4.9.337
- linux linux kernel4.10 and later · before 4.14.303
- linux linux kernel4.15 and later · before 4.19.270
- linux linux kernel4.20 and later · before 5.4.229
- linux linux kernel5.5 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.86
- linux linux kernel5.16 and later · before 6.0.16
- linux linux kernel3.6
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
- 61ebf0a926149cc161131470cf848cb70b3d6fe6, 0a1d9a860832a5ca43114cdebf0e8650463cc1f0, 5f54f145719f453dccc73304cd427096bf7b806c, 063ab9cb6308a0806d623c8d6dda5cb2b3b87fce, 3.6affected
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 6f28c7f67af4ef9bca580ab67ae2d4511797af56affected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before e738f82e5b1311e8fb3d1409491a6fcce6418fbeaffected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 1079df6acf56f99d86b0081a38c84701412cc90eaffected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 470a77989037c3ab2b08bf2d026d2c0ddc35ff5baffected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4affected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 88c6e0995c04b170563b5c894c50a3b2152e18c2affected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before b9decada8749b606fd8b4f04a3d6c74f7983d7bcaffected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before a6cffe54064a5f6c2162a85af3c16c6b453eac4eaffected · git
- c61e2775873f603148e8e998a938721b7d222d24 and later · before 725a521a18734f65de05b8d353b5bd0d3ca4c37aaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50518Oct 7, 2025 · parisc: Fix locking in pdc_iodc_print() firmware call31Monitor
- ← EarlierCVE-2022-50519Oct 7, 2025 · nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure22Monitor
- Later →CVE-2022-50521Oct 7, 2025 · platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1079df6acf56f99d86b0081a38c84701412cc90e | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 3.5 | Vendor (CNA) |
| Linux Linux | 3.6 | Vendor (CNA) |
| Linux Linux | 3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4 | Vendor (CNA) |
| Linux Linux | 470a77989037c3ab2b08bf2d026d2c0ddc35ff5b | Vendor (CNA) |
| Linux Linux | 6f28c7f67af4ef9bca580ab67ae2d4511797af56 | Vendor (CNA) |
| Linux Linux | 725a521a18734f65de05b8d353b5bd0d3ca4c37a | Vendor (CNA) |
| Linux Linux | 88c6e0995c04b170563b5c894c50a3b2152e18c2 | Vendor (CNA) |
| Linux Linux | a6cffe54064a5f6c2162a85af3c16c6b453eac4e | Vendor (CNA) |
| Linux Linux | b9decada8749b606fd8b4f04a3d6c74f7983d7bc | Vendor (CNA) |
| Linux Linux | e738f82e5b1311e8fb3d1409491a6fcce6418fbe | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/3991d98a8a07b71c02f3a39f77d6d9a7f575a5c4
- git.kernel.org/stable/c/470a77989037c3ab2b08bf2d026d2c0ddc35ff5b
- git.kernel.org/stable/c/6f28c7f67af4ef9bca580ab67ae2d4511797af56
- git.kernel.org/stable/c/725a521a18734f65de05b8d353b5bd0d3ca4c37a
- git.kernel.org/stable/c/88c6e0995c04b170563b5c894c50a3b2152e18c2
- git.kernel.org/stable/c/a6cffe54064a5f6c2162a85af3c16c6b453eac4e
- git.kernel.org/stable/c/b9decada8749b606fd8b4f04a3d6c74f7983d7bc
- git.kernel.org/stable/c/e738f82e5b1311e8fb3d1409491a6fcce6418fbe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.