In the mvpp2 network driver for the Linux kernel, received frames are written by hardware to memory starting at dma_addr plus MVPP2_SKB_HEADROOM. The CPU cache synchronization routine, however, begins at dma_addr and only covers a fixed length that includes the headroom and packet header but skips the packet tail. On systems that do not use coherent DMA, this mismatch allows the tail bytes of each frame to remain in a stale cache state. An attacker that can inject packets on the affected interface may read those stale bytes, potentially exposing data that had previously occupied the same physical memory region. This weakness corresponds to CWE‑682 (Inconsistent or Missing Object Initialization) and CWE‑821 (Improper Restriction of Operations within the Bounds of a Buffer).

Any Linux kernel that contains the unpatched mvpp2 driver for Marvell Ethernet devices is affected. The CPE list covers all 7.1 release candidates (rc1‑rc7) as well as the generic linux_kernel pattern, indicating that any kernel with the old synchronization logic is vulnerable. The CNA data lists the Linux vendor, with no specific hardware vendor mentioned in the advisory.

The CVSS score of 8.6 indicates high severity, and the EPSS score of <1% shows a very low probability of exploitation at present. The vulnerability is not present in the CISA KEV catalog, implying no widespread incidents have been reported. The likely attack vector is network‑based: an attacker would need to control packet reception on the affected interface to trigger the stale cache read. Because exploitation requires control of network traffic, the overall risk is moderate, but a successful attack could expose confidential data via stale cache reads.