VulnerabilityPublished 23 Oct 2026

CVE-2026-99028: Linux kernel · net: xilinx: axienet: Free outstanding DMA buffers on dmaengine stop

Source GCVE Database

Authoritative record:CVE-2026-99028· Medium

Not known to be exploited · fixed in eececf7c3a679d9c08175ad6bacbc8c31848f5af : update Linux kernel when convenient.

Data as of 26 Oct 2026, 16:00 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in eececf7c3a679d9c08175ad6bacbc8c31848f5af, bcf2573a68a808a5b54cadafa72b6672e662c2bf, 079396129da5e7cb40ca0920aa1b9525bef6097c +1

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-5xgg-2g43-r4gh

What to do

Upgrade Linux kernel to eececf7c3a679d9c08175ad6bacbc8c31848f5af, bcf2573a68a808a5b54cadafa72b6672e662c2bf, 079396129da5e7cb40ca0920aa1b9525bef6097c or 5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 6a91b846af85a24241decd686269e8e038eb13d1, < eececf7c3a679d9c08175ad6bacbc8c31848f5af	Fixed in eececf7c3a679d9c08175ad6bacbc8c31848f5af
LinuxLinux	Affected ≥ 6a91b846af85a24241decd686269e8e038eb13d1, < bcf2573a68a808a5b54cadafa72b6672e662c2bf	Fixed in bcf2573a68a808a5b54cadafa72b6672e662c2bf
LinuxLinux	Affected ≥ 6a91b846af85a24241decd686269e8e038eb13d1, < 079396129da5e7cb40ca0920aa1b9525bef6097c	Fixed in 079396129da5e7cb40ca0920aa1b9525bef6097c
LinuxLinux	Affected ≥ 6a91b846af85a24241decd686269e8e038eb13d1, < 5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58	Fixed in 5e5cf3ad7c099ff86ea9e422cddb25a2e5317b58
LinuxLinux	Affected =6.8	Fixed in–

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.

References

Community reviews

Loading reviews…