Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50659: hwrng: geode - Fix PCI device refcount leak

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Fixed version: Linux Linux 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c, 5cc818ad53df650cac8fb41d9066665366af3f03, 6b9e43c4098f1310f5b4d52121d007a219fa5d43.

Low priority for now. Upgrade to Linux Linux 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c, 5cc818ad53df650cac8fb41d9066665366af3f03, 6b9e43c4098f1310f5b4d52121d007a219fa5d43 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 20th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50659

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.18affected
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 88f4ea623f59155280d99d1a59a968f838472c4aaffected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before e2f44baf62567c5cfbc274974c7d96dddad53cccaffected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 6b9e43c4098f1310f5b4d52121d007a219fa5d43affected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 5cc818ad53df650cac8fb41d9066665366af3f03affected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before aa96aff394a511cc7bb7df08d1b8504d4d97671eaffected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 82bd423ed977847652b2048b0f8dcf049b1847a9affected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 874f798c2db5ad595e46982d7f727a679dacb048affected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0caffected · git
    • ef5d862734b84239e0140319a95fb0bbff5ef394 and later · before 9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50657Dec 9, 2025 · riscv: mm: add missing memcpy in kasan_init
    0Monitor
  • ← EarlierCVE-2022-50658Dec 9, 2025 · cpufreq: qcom: fix memory leak in error path
    0Monitor
  • Later →CVE-2022-50660Dec 9, 2025 · wifi: ipw2200: fix memory leak in ipw_wdev_init()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0cVendor (CNA)
Linux Linux5cc818ad53df650cac8fb41d9066665366af3f03Vendor (CNA)
Linux Linux6b9e43c4098f1310f5b4d52121d007a219fa5d43Vendor (CNA)
Linux Linux82bd423ed977847652b2048b0f8dcf049b1847a9Vendor (CNA)
Linux Linux874f798c2db5ad595e46982d7f727a679dacb048Vendor (CNA)
Linux Linux88f4ea623f59155280d99d1a59a968f838472c4aVendor (CNA)
Linux Linux9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445Vendor (CNA)
Linux Linuxaa96aff394a511cc7bb7df08d1b8504d4d97671eVendor (CNA)
Linux Linuxe2f44baf62567c5cfbc274974c7d96dddad53cccVendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records