CVE-2022-50659

hwrng: geode - Fix PCI device refcount leak

N/A
Published: December 9, 2025 at 01:29 AM UTC
Updated: June 17, 2026 at 05:23 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.18 ≤ v < 4.14.3032.6.18 ≤ v < 4.19.2702.6.18 ≤ v < 4.9.3372.6.18 ≤ v < 5.10.1632.6.18 ≤ v < 5.15.862.6.18 ≤ v < 5.4.2292.6.18 ≤ v < 6.0.162.6.18 ≤ v < 6.1.22.6.18 ≤ v < 6.22.6.18ef5d862734b84239e0140319a95fb0bbff5ef394
Vendor states this is fixed in 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c (fixed)
Vendor states this is fixed in 5cc818ad53df650cac8fb41d9066665366af3f03 (fixed)
Vendor states this is fixed in 6b9e43c4098f1310f5b4d52121d007a219fa5d43 (fixed)
Vendor states this is fixed in 82bd423ed977847652b2048b0f8dcf049b1847a9 (fixed)
Vendor states this is fixed in 874f798c2db5ad595e46982d7f727a679dacb048 (fixed)
Vendor states this is fixed in 88f4ea623f59155280d99d1a59a968f838472c4a (fixed)
Vendor states this is fixed in 9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445 (fixed)
Vendor states this is fixed in aa96aff394a511cc7bb7df08d1b8504d4d97671e (fixed)
Vendor states this is fixed in e2f44baf62567c5cfbc274974c7d96dddad53ccc (fixed)
Vendor states this is fixed in 2.6.18 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card