Local availability loss via PCI reference leak
Published Dec 9, 2025 · Updated May 11, 2026
Resource leak in the Linux kernel Geode RNG driver before 6.2 allows local users to reduce availability through retained PCI references. The driver exits for_each_pci_dev() with a non-null device pointer but omits pci_dev_put(), leaving the selected PCI device reference elevated on normal and error paths. The affected driver must run with compatible AMD Geode hardware; published assessments limit impact to availability and do not document a reliable unprivileged trigger.
Summary
What happened
Resource leak in the Linux kernel Geode RNG driver before 6.2 allows local users to reduce availability through retained PCI references. The driver exits for_each_pci_dev() with a non-null device pointer but omits pci_dev_put(), leaving the selected PCI device reference elevated on normal and error paths. The affected driver must run with compatible AMD Geode hardware; published assessments limit impact to availability and do not document a reliable unprivileged trigger.
The record
- CVE
- CVE-2022-50659
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=2.6.18
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <5cc818ad53df650cac8fb41d9066665366af3f03
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <6b9e43c4098f1310f5b4d52121d007a219fa5d43
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <82bd423ed977847652b2048b0f8dcf049b1847a9
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <874f798c2db5ad595e46982d7f727a679dacb048
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <88f4ea623f59155280d99d1a59a968f838472c4a
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <aa96aff394a511cc7bb7df08d1b8504d4d97671e
- Affected versionversion=ef5d862734b84239e0140319a95fb0bbff5ef394 <e2f44baf62567c5cfbc274974c7d96dddad53ccc
What conditions does exploitation require?
What is affected?
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
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