net: mana: Sync page pool RX frags for CPU
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.567.1.57.2In the Linux kernel, the following vulnerability has been resolved:
net: mana: Sync page pool RX frags for CPU
MANA allocates RX buffers from page pool fragments when frag_count is greater than 1. In that case the buffers remain DMA mapped by page pool and the RX completion path does not call dma_unmap_single(). As a result, the implicit sync-for-CPU normally performed by dma_unmap_single() is missing before the packet data is passed to the networking stack.
This breaks RX on configurations which require explicit DMA syncing, for example when booted with swiotlb=force.
Fix this by recording the page pool page and DMA sync offset when the RX buffer is allocated, and syncing the received packet range for CPU access before handing the RX buffer to the stack.
From the CVE record · Linux
The Linux kernel’s MANA driver fails to sync certain page-pool RX buffers for CPU access before passing packet data to the networking stack. This breaks receive traffic on configurations requiring explicit DMA syncing, such as those booted with swiotlb=force. The input does not specify an attacker path, authentication requirements, or user interaction.
Operators running Linux with the MANA network driver should check affected systems; affected kernel versions are not specified.