CVE-2026-53217
net: mvpp2: sync RX data at the hardware packet offset
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
25 Jun 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643https://git.kernel.org/stable/c/a13199fa224e9f776f4005d5037df03aa9ea8f37https://git.kernel.org/stable/c/a3ad9b5767c89531fc7dae951b51b0933dcf7051https://git.kernel.org/stable/c/bede0f481b9137d73d1cf64309cbe4b94818a5d6https://git.kernel.org/stable/c/e302206ad84a407a7e5f3f6fe767ff5efaace689