CVE-2022-50868

hwrng: amd - Fix PCI device refcount leak

N/A
Published: December 30, 2025 at 12:15 PM UTC
Updated: June 17, 2026 at 05:24 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.2%

Description

In the Linux kernel, the following vulnerability has been resolved: hwrng: amd - 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. Add the 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.1896d63c0297ccfd6d9059c614b3f5555d9441a2b3
Vendor states this is fixed in 1199f8e02941b326c60ab71a63002b7c80e38212 (fixed)
Vendor states this is fixed in 2b79a5e560779b35e1164d57ae35c48b43373082 (fixed)
Vendor states this is fixed in 2e10ecd012ae2b2a374b34f307e9bc1e6096c03d (fixed)
Vendor states this is fixed in 526c316948819d3ecd2bb20fe5e2580c51a1b760 (fixed)
Vendor states this is fixed in 5998e5c30e839f73e62cb29e0d9617b0d16ccba3 (fixed)
Vendor states this is fixed in cb348c7908631dd9f60083a0a1542eab055d3edf (fixed)
Vendor states this is fixed in e246f5eff26055bdcb61a2cc99c50af72a19680f (fixed)
Vendor states this is fixed in ecadb5b0111ea19fc7c240bb25d424a94471eb7d (fixed)
Vendor states this is fixed in f1c97f72ffd504f49882774e2ab689d982dc7afc (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