PoC Monitor
← All CVEs
CVE-2026-99079published 23 Oct 2026 12:23 UTCData: JSON · API

Linux

net/mlx5e: Prevent stale XSK buffer release on refill retry

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Prevent stale XSK buffer release on refill retry When an XDP redirect to an AF_XDP socket fails because its RX ring is full, the XSK core frees the buffer. During the subsequent batched refill of a legacy cyclic RQ, mlx5e also releases the WQE's XSK buffer before allocating a replacement. If that refill succeeds only partially, a WQE left without a replacement retains its old buffer pointer. The buffer can meanwhile be allocated to another WQE. A later refill retry can then free the live buffer through the stale pointer and publish the same UMEM frame twice. Mark the WQE as released immediately after the driver-side free. The flag is already cleared when a replacement buffer is assigned, so refill retries no longer release stale pointers. The failure is silent and produces no kernel warning or splat. A standalone legacy cyclic-RQ zero-copy libxsk reproducer, using 64-byte UDP traffic offered at 12 Mpps, detected it: stock stopped after 2,854,914 packets in 4.094 seconds, with 4,542 xdp_rx_ring_full events and 64 ownership/double-publication errors. With this change it processed 356,904,225 packets in 30 seconds despite 571,405 xdp_rx_ring_full events, with no ownership or data errors.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 3f93f82988bc6b4104314bf9aa485d47fbb7e241, < 32bbb870078d467479965c21bbc4960c57eea208
  • >= 3f93f82988bc6b4104314bf9aa485d47fbb7e241, < 34d1db2b18e1c1d189e34dd51923e031815f88e3
  • >= 3f93f82988bc6b4104314bf9aa485d47fbb7e241, < 639522e5056cade578a324acfa993ec6c9f7f5dc
  • >= 3f93f82988bc6b4104314bf9aa485d47fbb7e241, < 655f47477054d19de3b138840be229a1a4490d0c
  • >= 3f93f82988bc6b4104314bf9aa485d47fbb7e241, < e01620844c5c88b6fcf819d171df8e3976a0e76f

Fixed in 32bbb870078d467479965c21bbc4960c57eea208, 34d1db2b18e1c1d189e34dd51923e031815f88e3, 639522e5056cade578a324acfa993ec6c9f7f5dc, 655f47477054d19de3b138840be229a1a4490d0c, e01620844c5c88b6fcf819d171df8e3976a0e76f

Linux Linux
  • 6.4

Fixed in 0, 6.6.160, 6.12.113, 6.18.57, 7.2.11, 7.3

Mitigation

Upgrade Linux to 32bbb870078d467479965c21bbc4960c57eea208 or 34d1db2b18e1c1d189e34dd51923e031815f88e3 or 639522e5056cade578a324acfa993ec6c9f7f5dc or 655f47477054d19de3b138840be229a1a4490d0c or e01620844c5c88b6fcf819d171df8e3976a0e76f or later.

Upgrade Linux to 0 or 6.6.160 or 6.12.113 or 6.18.57 or 7.2.11 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published23 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.