net: atlantic: free RX pages of consumed but not refilled buffers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 46f4c29d9de6e4a9d4ed7de9a37dd42501d89f86 · < 782cc40b7ade4614a8aec0b948b8cf95c69f8d4b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: atlantic: free RX pages of consumed but not refilled buffers
aq_ring_rx_deinit() only walks [sw_head, sw_tail), the region posted to hardware. Since the page reuse strategy was added, a cleaned RX buffer keeps its page (and its DMA mapping) in the ring for reuse, and refill is batched: aq_ring_rx_fill() returns early until AQ_CFG_RX_REFILL_THRES slots are free. Slots that were consumed but not yet reposted therefore sit in the complementary [sw_tail, sw_head) gap with a live page, and the deinit walk never visits them: up to a refill batch worth of pages and DMA mappings leak on every interface down.
Walk the whole ring instead and release whatever is still there. Also bail out if the buffer ring is already gone: a partial aq_ptp_ring_alloc() failure frees the ring but leaves aq_nic set, so aq_ptp_ring_deinit() still gets here on the unwind path.
From the CVE record · Linux
The Linux kernel’s atlantic driver can leak RX pages and DMA mappings when an interface goes down because ring cleanup misses consumed buffers awaiting refill. The input does not describe an attacker-controlled trigger, authentication requirements, or user interaction.
Operators running Linux kernels with the atlantic driver should check their kernel’s vendor advisory; affected versions are not specified.