Vulnerability · Published Aug 15, 2026 · Assigned by Linux
CVE-2026-72064net: mana: Sync page pool RX frags for CPU
Critical 9.8
In plain English
A critical-severity race condition in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 43% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux | 7.0.0-34.34 | USN-8816-1 |
| Ubuntu:26.04:LTS | linux | 7.0.0-34.34 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1013.13 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1013.13 | USN-8816-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1013.13~24.04.1 | USN-8816-1 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1070.78 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1017.17 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1070.78~22.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1017.17~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1068.75 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1016.16 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1068.75~22.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1013.13 | USN-8816-2 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1013.13 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1013.13~24.04.1 | USN-8816-2 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1007.8 | USN-8816-4 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1007.8 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-34.34~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-34.34~24.04.1 | USN-8816-1 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1014.14 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1014.14 | USN-8816-1 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1024.25~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2022.23 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1014.14 | USN-8816-2 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1014.14 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1012.12 | USN-8816-1 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1012.12 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1012.12~24.04.1 | USN-8816-3 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1012.12~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1020.20 | USN-8816-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1020.20 | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-34.34.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-34.34.1 | USN-8816-1 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-34.34.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-34.34.1~24.04.1 | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-72064 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-72064 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 730ff06d3f5cc2ce0348414b78c10528b767d4a3 – before 845c959178ccab020b67bed7f4eae3058135ec80730ff06d3f5cc2ce0348414b78c10528b767d4a3 – before bc650dd5ce6434286b96e2b26a41af81f679cc7c730ff06d3f5cc2ce0348414b78c10528b767d4a3 – before c72a0f09c57f92113df69f9b902d11c9e4b132f5 |
| Linux | Linux | 6.18 |
Weakness: CWE-362 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H