net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure
CVE-2026-53229 · published 25 Jun 2026
How serious is it
- Severity: high, CVSS score 7.5 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-53229?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 84a0a2310d6de247335574649726cb000c7c0074 to < 3bad189a31eb78575ea69f093e8ef5b7e3e8c832, 84a0a2310d6de247335574649726cb000c7c0074 to < 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1, 84a0a2310d6de247335574649726cb000c7c0074 to < 2789b74ae1f4b68333c9d5eec2f3354d07b16e61, 84a0a2310d6de247335574649726cb000c7c0074 to < 0aabca726b43d833721034e97d99efcc8237b22a
- Linux Linux: 5.3
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure
In the XSK branch of mlx5e_xmit_xdp_buff(), when sq->xmit_xdp_frame()
returns false (e.g. XDPSQ is full), the function returns without
unmapping the DMA address or freeing the xdp_frame allocated by
xdp_convert_zc_to_xdp_frame(). The xdpi_fifo push only happens on
success, so the completion path cannot recover these entries.
With CONFIG_DMA_API_DEBUG=y, the leak surfaces on driver unbind:
DMA-API: pci 0000:08:00.0: device driver has pending DMA
allocations while released from device [count=1116]
One of leaked entries details: [device address=0x000000010ffd7028]
[size=1534 bytes] [mapped with DMA_TO_DEVICE] [mapped as phy]
WARNING: kernel/dma/debug.c:881 at dma_debug_device_change+0x127/0x180
...
DMA-API: Mapped at:
debug_dma_map_phys+0x4b/0xd0
dma_map_phys+0xfd/0x2d0
mlx5e_xdp_handle+0x5ae/0xac0 [mlx5_core]
mlx5e_xsk_skb_from_cqe_mpwrq_linear+0xc4/0x170 [mlx5_core]
mlx5e_handle_rx_cqe_mpwrq+0xc1/0x290 [mlx5_core]
Add the missing unmap + xdp_return_frame, matching the cleanup already
done in mlx5e_xdp_xmit(). has_frags is rejected earlier in this branch,
so no per-frag unmap is needed.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/3bad189a31eb78575ea69f093e8ef5b7e3e8c832
- git.kernel.org/stable/c/7b3eeba50fbc3b45f279037c29a87a90e8bac1e1
- git.kernel.org/stable/c/2789b74ae1f4b68333c9d5eec2f3354d07b16e61
- git.kernel.org/stable/c/0aabca726b43d833721034e97d99efcc8237b22a
- git.kernel.org/stable/c/b69004f5a6ad32da84d8aa5b23b9c0caafe6252e
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON