Skip to main content
VulnerabilityPublished Updated

CVE-2026-74386: Linux kernel · nvmet-tcp: fix page fragment cache leak in error path

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fc11e3f0daaadb6e600a86e54b089d4662d0a464 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fc11e3f0daaadb6e600a86e54b089d4662d0a464, ba3209704b3cd46961e4e081af5c52a780785648, a43a9abc1ebf663f0aa56a729106f68dd9c77da6 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < fc11e3f0daaadb6e600a86e54b089d4662d0a464
Fixed in
  • fc11e3f0daaadb6e600a86e54b089d4662d0a464
LinuxLinuxAffected
  • ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < ba3209704b3cd46961e4e081af5c52a780785648
Fixed in
  • ba3209704b3cd46961e4e081af5c52a780785648
LinuxLinuxAffected
  • ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < a43a9abc1ebf663f0aa56a729106f68dd9c77da6
Fixed in
  • a43a9abc1ebf663f0aa56a729106f68dd9c77da6
LinuxLinuxAffected
  • ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 5fbe83a374f09561a0f0c1f4aa021501ffd681eb
Fixed in
  • 5fbe83a374f09561a0f0c1f4aa021501ffd681eb
LinuxLinuxAffected
  • ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 4dae393956093c807212918fd91a8fc70df15338
Fixed in
  • 4dae393956093c807212918fd91a8fc70df15338
LinuxLinuxAffected
  • =5.0
Fixed in–

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.

References

Community reviews

Loading reviews…