Look up another CVE · open CVE-2026-53217 in the interactive tracker
CVE-2026-53217
net: mvpp2: sync RX data at the hardware packet offset
Published 2026-06-25 (4 months ago) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-53217 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4665-1 · 2026-07-03 · text | 6.1.176-1 | Update the kernel and reboot. DLA-4665-1 shipped the fix on 2026-07-03, in 6.1.176-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
- What this is
- MARVELL MVPP2 ETHERNET DRIVERMAINTAINERS section matched on drivers/net/ethernet/marvell/mvpp2/ · netdev@vger.kernel.org · Maintained
- Kernel module
- mvpp2
Check it on the machine
grep -wE 'CONFIG_ETHERNET|CONFIG_MVPP2|CONFIG_NET_VENDOR_MARVELL' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w mvpp2Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
- trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/cloud-arm64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_ETHERNET, CONFIG_MVPP2, CONFIG_NET_VENDOR_MARVELL
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-06-25 (4 months ago)source
- CVSS
- 8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:Lsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.38%, higher than 30.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/net
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.5 | 5.10.259 | 60412bdd1b25 |
| 5.5 | 5.15.210 | 19f8bc139e9b |
| 5.5 | 6.1.176 | a3ad9b5767c8 |
| 5.5 | 6.6.143 | bede0f481b91 |
| 5.5 | 6.12.94 | 23548007b3c6 |
| 5.5 | 6.18.36 | a13199fa224e |
| 5.5 | 7.0.13 | e302206ad84a |
| 5.5 | 7.1 | 180235600934 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4671-1 | 2026-07-05 | bullseye 6.1.176-1~deb11u1 | tracker |
| DLA-4665-1 | 2026-07-03 | bookworm 6.1.176-1 | tracker |
| DLA-4664-1 | 2026-07-03 | bullseye 5.10.259-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- The vulnerable code is in the Ethernet RX path and is reached by packets received on an affected mvpp2 network interface. A remote peer can trigger it by sending network traffic to a system using this driver.
- AC:LAttack complexity, low
- On affected non-coherent DMA deployments, exploitation only requires sending received frames that traverse the normal RX/NAPI path. There is no race or attacker-uncontrolled timing requirement in the vulnerable path.
- PR:NPrivileges required, none
- No local privileges or authentication are required to reach the receive path. The attacker only needs network reachability to the affected interface.
- UI:NUser interaction, none
- Packet reception and processing happen automatically once the interface is up. No user action is required.
- S:UScope, unchanged
- The bug affects packet data handled within the same kernel/network-device security authority. It does not cross a VM, IOMMU, or other separate security boundary.
- C:HConfidentiality impact, high
- The incorrect DMA sync can leave stale cache contents in the tail of received skbs, potentially exposing previous packet-buffer contents through delivery, forwarding, or reflection. Repeated remote triggering can disclose more than a few bounded bytes of network data over time.
- I:LIntegrity impact, low
- The CPU-visible packet tail can differ from the actual frame written by hardware, corrupting data delivered to XDP, the network stack, or applications. This is packet/data integrity loss, but not an arbitrary kernel memory write or control-flow primitive.
- A:LAvailability impact, low
- An attacker can repeatedly cause corrupted received packets, leading to packet drops, protocol failures, or degraded network service. The investigated path does not indicate a kernel panic, hang, or reliable full-system DoS.