# CVE-2026-53217: net: mvpp2: sync RX data at the hardware packet offset

> An attacker on non-coherent DMA systems can read stale cache contents from the end of received network frames due to incorrect DMA synchronization in the mvpp2 driver.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-53217, DEBIAN-CVE-2026-53217, GHSA-vj9r-56j4-wwmh, ROOT-OS-DEBIAN-11-CVE-2026-53217, ROOT-OS-DEBIAN-12-CVE-2026-53217, ROOT-OS-UBUNTU-2204-CVE-2026-53217, ROOT-OS-UBUNTU-2404-CVE-2026-53217, UBUNTU-CVE-2026-53217

## What is CVE-2026-53217?

CVE-2026-53217 is a high-severity vulnerability in Linux kernel, published on 25 Jun 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: mvpp2: sync RX data at the hardware packet offset

mvpp2 programs the RX queue packet offset, so hardware writes received
data at dma_addr + MVPP2_SKB_HEADROOM. The current CPU sync starts at
dma_addr and only covers rx_bytes + MVPP2_MH_SIZE bytes, which syncs the
unused headroom and misses the same number of bytes at the packet tail.

On non-coherent DMA systems this can leave the CPU reading stale cache
contents for the end of the received frame.

Use dma_sync_single_range_for_cpu() with MVPP2_SKB_HEADROOM as the range
offset so the sync covers the Marvell header and packet data actually
written by hardware.

Weakness: CWE-682 (Incorrect Calculation)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53217 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53217 is a high-severity vulnerability in Linux kernel, published on 25 Jun 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-53217 in the wild and no public exploit code.

Affected product: Linux kernel. 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-53217/ (Markdown: https://insights.sbomify.com/CVE-2026-53217/index.md)
```

## Sources

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

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