# CVE-2026-53215: net: mvpp2: refill RX buffers before XDP or skb use

> A use-after-free vulnerability in the Marvell mvpp2 network driver allows attackers to cause memory corruption or denial of service by triggering RX buffer errors.

- **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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-53215, DEBIAN-CVE-2026-53215, GHSA-37pv-m98r-vgm8, ROOT-OS-DEBIAN-11-CVE-2026-53215, ROOT-OS-DEBIAN-12-CVE-2026-53215, ROOT-OS-UBUNTU-2204-CVE-2026-53215, ROOT-OS-UBUNTU-2404-CVE-2026-53215, UBUNTU-CVE-2026-53215

## What is CVE-2026-53215?

CVE-2026-53215 is a critical use after free 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: refill RX buffers before XDP or skb use

The RX error path returns the current descriptor buffer to the hardware
BM pool. That is only valid while the driver still owns the buffer.

mvpp2_rx_refill() can fail after the current buffer has been handed to
XDP or attached to an skb. In those cases mvpp2_run_xdp() may have
recycled, redirected, or queued the page for XDP_TX, and an skb free also
retires the data buffer. Returning such a buffer to BM lets hardware DMA
into memory that is no longer owned by the RX ring.

Refill the BM pool before handing the current buffer to XDP or to the
skb. If the allocation fails there, drop the packet and return the
still-owned current buffer to BM, preserving the pool depth. Once the
refill succeeds, later local drops retire/free the current buffer instead
of returning it to BM.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53215 being exploited?

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

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

## Sources

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

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