# CVE-2026-53216: net: mvpp2: limit XDP frame size to the RX buffer

> A flaw in the Linux kernel mvpp2 driver allows memory corruption via XDP tail adjustment, potentially leading to code execution or denial of service.

- **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:** 25 Jun 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-53216, DEBIAN-CVE-2026-53216, GHSA-8vc2-h54q-6258, ROOT-OS-DEBIAN-11-CVE-2026-53216, ROOT-OS-DEBIAN-12-CVE-2026-53216, ROOT-OS-UBUNTU-2204-CVE-2026-53216, ROOT-OS-UBUNTU-2404-CVE-2026-53216, UBUNTU-CVE-2026-53216

## What is CVE-2026-53216?

CVE-2026-53216 is a critical memory corruption 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: limit XDP frame size to the RX buffer

mvpp2 has short and long BM pools, and short pool buffers can be smaller
than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with
PAGE_SIZE as frame size.

XDP helpers use frame_sz to validate tail growth and to derive the hard
end of the data area. Advertising PAGE_SIZE for short buffers can let
bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting
memory or later tripping skb tailroom checks.

Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches
the actual buffer backing the packet.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53216 being exploited?

There is no known exploitation of CVE-2026-53216 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-53216 and fix it if it is affected.

What it is: CVE-2026-53216 is a critical memory corruption 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-53216 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-53216/ (Markdown: https://insights.sbomify.com/CVE-2026-53216/index.md)
```

## Sources

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

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