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-50576serial: pch: Fix PCI device refcount leak in pch_request_dma()

Description

In the Linux kernel, the following vulnerability has been resolved: serial: pch: Fix PCI device refcount leak in pch_request_dma() As comment of pci_get_slot() says, it returns a pci_device with its refcount increased. The caller must decrement the reference count by calling pci_dev_put(). Since 'dma_dev' is only used to filter the channel in filter(), we can call pci_dev_put() before exiting from pch_request_dma(). Add the missing pci_dev_put() for the normal and error path.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 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.25% · top 84% of all CVEs (16 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 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 90ff030ca10b69feeebda1427550ebf9ed2ad868
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 56e5a7c5ee3f0dc8978b5df2b1a98a1b060c5e2a
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < dfd15c5550b9190d5b0f9bcacb3e6436322f3854
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < d165388227aa7e46a9751b90bae6337b5335cdbb
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 07f4ca68b0f6bf84b6b391c14b59fd179fcde9c5
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 6f7d82380fbeaed3a940efc33c23f0c4bbd0fc02
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 4f5d28865c665c9064de631a518f9bc8099d9ce4
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 516614a371c26e3334625b4bca19a5362bf658d6
    • affected 3c6a483275f47a2ef7119309ad3d791c10cf30da – < 8be3a7bf773700534a6e8f87f6ed2ed111254be5
  • Linux · Linux

    • affected 2.6.38
    • unaffected < 2.6.38
    • 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-50576 badge
[![CVE-2022-50576](https://cveledger.app/badge/CVE-2022-50576.svg)](https://cveledger.app/cve/CVE-2022-50576)

Record last updated .