Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.30% · top 77% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 88f4ea623f59155280d99d1a59a968f838472c4a
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < e2f44baf62567c5cfbc274974c7d96dddad53ccc
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 6b9e43c4098f1310f5b4d52121d007a219fa5d43
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 5cc818ad53df650cac8fb41d9066665366af3f03
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < aa96aff394a511cc7bb7df08d1b8504d4d97671e
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 82bd423ed977847652b2048b0f8dcf049b1847a9
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 874f798c2db5ad595e46982d7f727a679dacb048
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 19b7b85773b18457ff85a9ff4f5e2a2d4bf7ed0c
    • affected ef5d862734b84239e0140319a95fb0bbff5ef394 – < 9f6ec8dc574efb7f4f3d7ee9cd59ae307e78f445
  • Linux · Linux

    • affected 2.6.18
    • unaffected < 2.6.18
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50659 badge
[![CVE-2022-50659](https://cveledger.app/badge/CVE-2022-50659.svg)](https://cveledger.app/cve/CVE-2022-50659)

Record last updated .