Skip to main content
VulnerabilityPublished Updated

CVE-2026-80862: Linux kernel · nvme-tcp: fix usage of page_frag_cache

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d19f98c79f1b7e09e4cdf5c20d626e571e487467, 64561afb42d8390695bf810d9bbd087cbca00291, 36ac05f7cfd59d90c597071304b14e98090d5dd1 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 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
  • >=6.6.160 <6.7
Fixed in
  • d19f98c79f1b7e09e4cdf5c20d626e571e487467
  • 64561afb42d8390695bf810d9bbd087cbca00291
  • 36ac05f7cfd59d90c597071304b14e98090d5dd1
  • 6e4cf281558709b92ec2ca3054fe2ffc69266ef9
  • 6.7
  • 0a9750263ffacbbd2048a391fd4bd22e2146c57d
LinuxLinuxAffected
  • =6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix usage of page_frag_cache nvme uses page_frag_cache to preallocate PDU for each preallocated request of block device. Block devices are created in parallel threads, consequently page_frag_cache is used in not thread-safe manner. That leads to incorrect refcounting of backstore pages and premature free. That can be catched by !sendpage_ok inside network stack: WARNING: CPU: 7 PID: 467 at ../net/core/skbuff.c:6931 skb_splice_from_iter+0xfa/0x310. tcp_sendmsg_locked+0x782/0xce0 tcp_sendmsg+0x27/0x40 sock_sendmsg+0x8b/0xa0 nvme_tcp_try_send_cmd_pdu+0x149/0x2a0 Then random panic may occur. Fix that by serializing the usage of page_frag_cache.

References

Community reviews

Loading reviews…