CVE-2026-99028net: xilinx: axienet: Free outstanding DMA buffers on dmaengine stop
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net: xilinx: axienet: Free outstanding DMA buffers on dmaengine stop In the dmaengine path the driver pre-submits RX buffers and holds in-flight TX buffers whose SKBs are DMA-mapped by the driver and freed only in the completion callbacks. On ndo_stop() dmaengine_terminate_sync() aborts these descriptors without running their callbacks, and the driver then frees only the ring shells, leaking every SKB still owned by the engine and its DMA mapping on each ifdown. With 128 RX buffers pre-posted per channel, the mapping leak can eventually exhaust a limited IOMMU aperture. Clear the slot's skb in the TX and RX callbacks so a non-NULL skb marks a slot that still owns a live, DMA-mapped buffer, and on stop unmap and free every such buffer. axienet_dma_rx_cb() runs from the DMA tasklet and re-arms the RX ring on each completion, so it can race axienet_stop(): a completion may submit a fresh buffer after dmaengine_terminate_sync() has returned, leaving the channel armed with a buffer the teardown then frees while the engine may still write into it (dma_release_channel() does not stop it either). Add a lock that axienet_dma_rx_cb() holds across the @stopping check and the resubmit, and axienet_stop() holds to set @stopping before terminating. Once @stopping is set no callback can arm a new buffer, and any armed just before is aborted by the terminate, so teardown only frees buffers the engine no longer owns.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 23, 2026
- First seen by InfoSec Signals
- Oct 23, 2026
Affected products
Linux Linux linux:linux (from the name) | from 6a91b846af85a24241decd686269e8e038eb13d1 before 079396129da5e7cb40ca0920aa1b9525bef6097c; from 6a91b846af85a24241decd686269e8e038eb13d1 before eececf7c3a679d9c08175ad6bacbc8c31848f5af; 6a91b846af85a24241decd686269e8e038eb13d1 builds before 5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58; from 6a91b846af85a24241decd686269e8e038eb13d1 before bcf2573a68a808a5b54cadafa72b6672e662c2bf | CNA record |
References
- https://git.kernel.org/stable/c/079396129da5e7cb40ca0920aa1b9525bef6097c
- https://git.kernel.org/stable/c/eececf7c3a679d9c08175ad6bacbc8c31848f5af
- https://git.kernel.org/stable/c/5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58
- https://git.kernel.org/stable/c/bcf2573a68a808a5b54cadafa72b6672e662c2bf
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.