The Linux kernel MANA network driver allocates RX buffers from page pool fragments when frag_count is greater than one. In this scenario, the buffers remain DMA mapped by the page pool, but the RX completion path fails to call dma_unmap_single(), which normally performs an implicit sync-for-CPU operation. Without this synchronization, packet data passed to the networking stack may be stale or inconsistent on systems requiring explicit DMA syncing (e.g., swiotlb=force). The vulnerability breaks RX functionality under these conditions. The patch fixes this by tracking the page pool page and DMA sync offset during RX buffer allocation and explicitly syncing the received packet range for CPU access before handing it off.

This vulnerability causes the received network packets to be unsynchronized for CPU access on affected configurations, potentially leading to broken RX functionality or corrupted packet data in the networking stack. It primarily impacts systems that require explicit DMA synchronization, such as those booted with swiotlb=force. There is no indication of direct security compromise or exploitation in the wild.

A fix has been implemented in the Linux kernel to address this issue by ensuring proper DMA synchronization of RX buffers allocated from page pool fragments. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and remediation guidance.