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-48973

gpio: amd8111: Fix PCI device reference count leak

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: amd8111: Fix PCI device reference count 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() after the 'out' label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the 'Device not found' branch. For the normal path, add pci_dev_put() in amd_gpio_exit().

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 19 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

CVSS scores of CVE-2022-48973, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 4749c5cc147c9860b96db1e71cc36d1de1bd3f59
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 71d591ef873f9ebb86cd8d053b3caee785b2de6a
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < b2bc053ebbba57a06fa655db5ea796de2edce445
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 48bd5d3801f6b67cc144449d434abbd5043a6d37
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 5ee6413d3dd972930af787b2c0c7aaeb379fa521
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 4271515f189bd5fe2ec86b4089dab7cb804625d2
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < e364ce04d8f840478b09eee57b614de7cf1e743e
    • affected f942a7de047d8c599cc1a9a26293c8c7400450ea – < 45fecdb9f658d9c82960c98240bc0770ade19aca
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 4.9.336 – ≤ 4.9.*
    • unaffected 4.14.302 – ≤ 4.14.*
    • unaffected 4.19.269 – ≤ 4.19.*
    • unaffected 5.4.227 – ≤ 5.4.*
    • unaffected 5.10.159 – ≤ 5.10.*
    • unaffected 5.15.83 – ≤ 5.15.*
    • unaffected 6.0.13 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .