Skip to main content
VulnerabilityPublished Updated

CVE-2026-72064: Linux kernel · Race Condition

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in c72a0f09c57f92113df69f9b902d11c9e4b132f5 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in c72a0f09c57f92113df69f9b902d11c9e4b132f5, bc650dd5ce6434286b96e2b26a41af81f679cc7c, 845c959178ccab020b67bed7f4eae3058135ec80
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Linux kernel to c72a0f09c57f92113df69f9b902d11c9e4b132f5, bc650dd5ce6434286b96e2b26a41af81f679cc7c or 845c959178ccab020b67bed7f4eae3058135ec80.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 730ff06d3f5cc2ce0348414b78c10528b767d4a3, < c72a0f09c57f92113df69f9b902d11c9e4b132f5
Fixed in
  • c72a0f09c57f92113df69f9b902d11c9e4b132f5
LinuxLinuxAffected
  • ≥ 730ff06d3f5cc2ce0348414b78c10528b767d4a3, < bc650dd5ce6434286b96e2b26a41af81f679cc7c
Fixed in
  • bc650dd5ce6434286b96e2b26a41af81f679cc7c
LinuxLinuxAffected
  • ≥ 730ff06d3f5cc2ce0348414b78c10528b767d4a3, < 845c959178ccab020b67bed7f4eae3058135ec80
Fixed in
  • 845c959178ccab020b67bed7f4eae3058135ec80
LinuxLinuxAffected
  • =6.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net: mana: Sync page pool RX frags for CPU MANA allocates RX buffers from page pool fragments when frag_count is greater than 1. In that case the buffers remain DMA mapped by page pool and the RX completion path does not call dma_unmap_single(). As a result, the implicit sync-for-CPU normally performed by dma_unmap_single() is missing before the packet data is passed to the networking stack. This breaks RX on configurations which require explicit DMA syncing, for example when booted with swiotlb=force. Fix this by recording the page pool page and DMA sync offset when the RX buffer is allocated, and syncing the received packet range for CPU access before handing the RX buffer to the stack.

References

Community reviews

Loading reviews…