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-74386nvmet-tcp: fix page fragment cache leak in error path

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix page fragment cache leak in error path In nvmet_tcp_alloc_queue(), when a connection is closed during the allocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN), the error handling jumps to out_destroy_sq and then to out_ida_remove without draining the page fragment cache. Although nvmet_tcp_free_cmd() is called in some error paths to release individual page fragments, the underlying page cache reference held by queue->pf_cache is never released. The first allocation using pf_cache is the call to nvmet_tcp_alloc_cmd() for queue->connect, which happens after ida_alloc() returns successfully. This results in a page leak each time a connection fails during allocation, which could lead to memory exhaustion over time if connections are repeatedly opened and closed. Fix this by calling page_frag_cache_drain() before freeing the queue structure in the out_ida_remove label.

Timeline

  1. ID reserved

    By Linux

  2. Published

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

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (17 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 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < aadb8eb9006e192c51b499860f40765de7d55680
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < fc11e3f0daaadb6e600a86e54b089d4662d0a464
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < a43a9abc1ebf663f0aa56a729106f68dd9c77da6
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < ba3209704b3cd46961e4e081af5c52a780785648
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 5fbe83a374f09561a0f0c1f4aa021501ffd681eb
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 4dae393956093c807212918fd91a8fc70df15338
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .