# CVE-2026-72064: net: mana: Sync page pool RX frags for CPU

> Missing DMA synchronization in the MANA network driver causes RX failures and denial of service on systems using swiotlb=force.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-72064, DEBIAN-CVE-2026-72064, GHSA-fh7x-649r-3p95, UBUNTU-CVE-2026-72064

## What is CVE-2026-72064?

CVE-2026-72064 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-72064?


## How do I fix CVE-2026-72064?

Apply the vendor's patch.

## Is CVE-2026-72064 being exploited?

There is no known exploitation of CVE-2026-72064 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72064 and fix it if it is affected.

What it is: CVE-2026-72064 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72064 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72064/ (Markdown: https://insights.sbomify.com/CVE-2026-72064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72064
- OSV: https://osv.dev/vulnerability/CVE-2026-72064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72064/
Summaries are generated and may contain mistakes; the official description above is the record.