Linux Kernel up to 6.1.1 hwrng for_each_pci_dev reference count

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.1.1 and classified as critical. This affects the function for_each_pci_dev of the component hwrng. Performing a manipulation results in reference count. This vulnerability is identified as CVE-2022-50868. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.1. It has been classified as critical. This affects the function for_each_pci_dev of the component hwrng. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50868 since 12/30/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 281558 (Linux Distros Unpatched Vulnerability : CVE-2022-50868), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16 or 6.1.2 eliminates this vulnerability. Applying the patch f1c97f72ffd504f49882774e2ab689d982dc7afc/526c316948819d3ecd2bb20fe5e2580c51a1b760/e246f5eff26055bdcb61a2cc99c50af72a19680f/1199f8e02941b326c60ab71a63002b7c80e38212/5998e5c30e839f73e62cb29e0d9617b0d16ccba3/2b79a5e560779b35e1164d57ae35c48b43373082/cb348c7908631dd9f60083a0a1542eab055d3edf/2e10ecd012ae2b2a374b34f307e9bc1e6096c03d/ecadb5b0111ea19fc7c240bb25d424a94471eb7d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (281558) and CERT Bund (WID-SEC-2025-2941). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • IBM Power Hardware Management Console
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • IBM DataPower Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Reference count
CWE: CWE-911 / CWE-664
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 281558
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50868

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.9.337/4.14.303/4.19.270/5.4.229/5.10.163/5.15.86/6.0.16/6.1.2
Patch: f1c97f72ffd504f49882774e2ab689d982dc7afc/526c316948819d3ecd2bb20fe5e2580c51a1b760/e246f5eff26055bdcb61a2cc99c50af72a19680f/1199f8e02941b326c60ab71a63002b7c80e38212/5998e5c30e839f73e62cb29e0d9617b0d16ccba3/2b79a5e560779b35e1164d57ae35c48b43373082/cb348c7908631dd9f60083a0a1542eab055d3edf/2e10ecd012ae2b2a374b34f307e9bc1e6096c03d/ecadb5b0111ea19fc7c240bb25d424a94471eb7d

Timelineinfo

12/30/2025 Advisory disclosed
12/30/2025 +0 days CVE reserved
12/30/2025 +0 days VulDB entry created
04/26/2026 +117 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50868 (🔒)
GCVE (CVE): GCVE-0-2022-50868
GCVE (VulDB): GCVE-100-338901
CERT Bund: WID-SEC-2025-2941 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 12/30/2025 16:18
Updated: 04/26/2026 07:13
Changes: 12/30/2025 16:18 (59), 01/01/2026 00:17 (7), 01/01/2026 05:17 (2), 01/28/2026 00:17 (1), 04/26/2026 07:13 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!