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.

A flaw was found in the Linux kernel's mvpp2 network driver. This issue occurs because the driver incorrectly synchronizes received (RX) data at the hardware packet offset. On systems with non-coherent Direct Memory Access (DMA), this can lead to the Central Processing Unit (CPU) reading stale cache contents instead of the actual received network frame data. This vulnerability could result in information disclosure.

Red Hat Enterprise Linux 10 Not affected kernel Red Hat Enterprise Linux 6 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel-rt Red Hat Enterprise Linux 8 Not affected kernel Red Hat Enterprise Linux 8 Not affected kernel-rt Red Hat Enterprise Linux 9 Not affected kernel Red Hat Enterprise Linux 9 Not affected kernel-rt https://www.cve.org/CVERecord?id=CVE-2026-53217 https://nvd.nist.gov/vuln/detail/CVE-2026-53217 https://lore.kernel.org/linux-cve-announce/2026062504-CVE-2026-53217-ff47@gregkh/T