# hwrng: geode - Fix PCI device refcount leak

CVE record · `CVE-2022-50659`

- **Identifiers:** `CVE-2022-50659`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 9 Dec 2025, 01:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 88f4ea623f59155280d99d1a59a968f838472c4a` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before e2f44baf62567c5cfbc274974c7d96dddad53ccc` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 6b9e43c4098f1310f5b4d52121d007a219fa5d43` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 5cc818ad53df650cac8fb41d9066665366af3f03` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before aa96aff394a511cc7bb7df08d1b8504d4d97671e` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 82bd423ed977847652b2048b0f8dcf049b1847a9` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 874f798c2db5ad595e46982d7f727a679dacb048` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c` (git)
  - affected: `ef5d862734b84239e0140319a95fb0bbff5ef394 to before 9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.18`
  - unaffected: `before 2.6.18` (semver)
  - unaffected: `4.9.337 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.303 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.270 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.229 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.163 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.86 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.16 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.2 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 22nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 Dec 2025, 16:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50659)

## Sources

- [CVE List: CVE-2022-50659](https://www.cve.org/CVERecord?id=CVE-2022-50659)
- [NVD: CVE-2022-50659](https://nvd.nist.gov/vuln/detail/CVE-2022-50659)

### References from the CNA

- <https://git.kernel.org/stable/c/88f4ea623f59155280d99d1a59a968f838472c4a>
- <https://git.kernel.org/stable/c/e2f44baf62567c5cfbc274974c7d96dddad53ccc>
- <https://git.kernel.org/stable/c/6b9e43c4098f1310f5b4d52121d007a219fa5d43>
- <https://git.kernel.org/stable/c/5cc818ad53df650cac8fb41d9066665366af3f03>
- <https://git.kernel.org/stable/c/aa96aff394a511cc7bb7df08d1b8504d4d97671e>
- <https://git.kernel.org/stable/c/82bd423ed977847652b2048b0f8dcf049b1847a9>
- <https://git.kernel.org/stable/c/874f798c2db5ad595e46982d7f727a679dacb048>
- <https://git.kernel.org/stable/c/19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c>
- <https://git.kernel.org/stable/c/9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50659>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50659/>. Everything for agents: <https://agentprime.io/llms.txt>.
