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-2026-80821nvmet: pci-epf: put CQ ref on create_cq mapping failure

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: put CQ ref on create_cq mapping failure nvmet_pci_epf_create_cq() calls nvmet_cq_create(), which takes a reference on the controller and installs the completion queue. If the subsequent PCI address-space mapping fails or returns a too-small partial mapping, the function jumps to err_internal / err_unmap_queue without calling nvmet_cq_put(). The matching put in nvmet_pci_epf_delete_cq() is gated on NVMET_PCI_EPF_Q_LIVE, which is only set after the mapping succeeds, so teardown never releases these references. A remote PCI host that drives Create IO CQ commands with a failing PRP1/pci_addr therefore leaks the CQ and a controller reference on each attempt. Drop the CQ reference on the mapping-failure paths. The err_internal and err_unmap_queue labels are only reachable after nvmet_cq_create() has succeeded, so this pairs the create/put correctly.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days 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: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (19 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 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 – < f31650243c1ab32394077f234685e89ed8dece84
    • affected 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 – < b5f97fae2503a763fa0f953abf5f121b0fef7d0d
    • affected 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 – < 56a7b6a6880dbabe28214ff88df8d229ca3a944a
    • affected 0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 – < 659ae9d02cb5d72c76f74fff7441eb8fb64d8f5c
  • Linux · Linux

    • affected 6.14
    • unaffected < 6.14
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .