CVE-2026-99028

net: xilinx: axienet: Free outstanding DMA buffers on dmaengine stop

Description

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.

Key facts

Published
23 Oct 2026
Last changed
23 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.247% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 6a91b846af85a24241decd686269e8e038eb13d1 up to but excluding 079396129da5e7cb40ca0920aa1b9525bef6097c (affected)
  • 6a91b846af85a24241decd686269e8e038eb13d1 up to but excluding eececf7c3a679d9c08175ad6bacbc8c31848f5af (affected)
  • 6a91b846af85a24241decd686269e8e038eb13d1 up to but excluding 5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58 (affected)
  • 6a91b846af85a24241decd686269e8e038eb13d1 up to but excluding bcf2573a68a808a5b54cadafa72b6672e662c2bf (affected)
LinuxLinux
  • Default status: affected
  • 6.8 (affected)
  • 0 up to but excluding 6.8 (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.58 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References