# CVE-2022-50868: linux: In the Linux kernel, the following vulnerability has been resolved:  hwrng: amd - Fix PCI device refcount leak  for_e...

CVE-2022-50868 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50868, released December 30, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2022-50868
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0024
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Dec 30, 2025

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.1.4-1 | [DEBIAN-CVE-2022-50868](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50868.md) | Dec 30, 2025 |
| Linux | linux Debian 13.5 (trixie) | 6.1.4-1 | [DEBIAN-CVE-2022-50868](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50868.md) | Dec 30, 2025 |
| Linux | linux Debian 14 | 6.1.4-1 | [DEBIAN-CVE-2022-50868](https://patchblox.com/security/data/fix/linux/debian-cve-2022-50868.md) | Dec 30, 2025 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.