CVE-2026-53229

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
37.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (4)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b69004f5a6ad32da84d8aa5b23b9c0caafe6252e
generic

net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b3eeba50fbc3b45f279037c29a87a90e8bac1e1
generic

net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2789b74ae1f4b68333c9d5eec2f3354d07b16e61
generic

net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0aabca726b43d833721034e97d99efcc8237b22a

Vendor Advisories for CVE-2026-53229(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 38× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:17 UTCEG score recompute
  2. 2026-07-07 00:17 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:19 UTCEG score recompute
  6. 2026-07-06 13:19 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:19 UTCEG score recompute
  10. 2026-07-06 02:19 UTCGHSA enrichment
  11. 2026-07-05 15:21 UTCEG score recompute
  12. 2026-07-05 15:21 UTCGHSA enrichment
  13. 2026-07-05 04:22 UTCEG score recompute
  14. 2026-07-05 04:22 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 17:23 UTCEG score recompute
  18. 2026-07-04 17:23 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:26 UTCEG score recompute
  22. 2026-07-04 06:25 UTCGHSA enrichment
  23. 2026-07-03 19:24 UTCEG score recompute
  24. 2026-07-03 19:24 UTCGHSA enrichment
  25. 2026-07-03 08:26 UTCEG score recompute
Show 25 more
  1. 2026-07-03 08:26 UTCGHSA enrichment
  2. 2026-07-02 21:29 UTCEG score recompute
  3. 2026-07-02 21:29 UTCGHSA enrichment
  4. 2026-07-02 10:30 UTCEG score recompute
  5. 2026-07-02 10:30 UTCGHSA enrichment
  6. 2026-07-01 23:31 UTCEG score recompute
  7. 2026-07-01 23:31 UTCGHSA enrichment
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-07-01 12:33 UTCEG score recompute
  10. 2026-07-01 12:33 UTCGHSA enrichment
  11. 2026-07-01 01:35 UTCEG score recompute 7.50
  12. 2026-07-01 01:35 UTCGHSA enrichment
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  18. 2026-06-28 05:52 UTCEG score recompute
  19. 2026-06-28 05:51 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 10:07 UTCEG score recompute
  25. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53229?
CVE-2026-53229 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: xsk: Fix DMA and xdpframe leak on XDPTX xmit failure In the XSK branch of mlx5exmitxdpbuff(), when sq->xmitxdp_frame() returns false (e.g. XDPSQ is full), the function returns without unmapping the DMA address or freeing…
When was CVE-2026-53229 disclosed?
CVE-2026-53229 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53229 actively exploited?
CVE-2026-53229 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53229?
CVE-2026-53229 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53229?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53229, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53229

Explore →

Is Your Infrastructure Affected by CVE-2026-53229?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.