CVE-2026-53229

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 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(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 64× 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.

Showing the most recent 100 of 219 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:38 UTCEG score recompute
  11. 2026-08-30 19:38 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 23:59 UTCEG score recompute
  16. 2026-08-27 23:59 UTCGHSA enrichment
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 00:13 UTCEG score recompute
  21. 2026-08-25 00:13 UTCGHSA enrichment
  22. 2026-08-24 13:13 UTCEG score recompute
  23. 2026-08-24 13:13 UTCGHSA enrichment
  24. 2026-08-23 20:23 UTCGHSA enrichment
  25. 2026-08-23 09:25 UTCEG score recompute
Show 75 more
  1. 2026-08-23 09:25 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-22 22:28 UTCGHSA enrichment
  4. 2026-08-22 10:43 UTCEG score recompute
  5. 2026-08-22 10:43 UTCGHSA enrichment
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 17:26 UTCGHSA enrichment
  8. 2026-08-21 05:09 UTCEG score recompute
  9. 2026-08-21 05:09 UTCGHSA enrichment
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 18:06 UTCGHSA enrichment
  12. 2026-08-20 07:09 UTCEG score recompute
  13. 2026-08-20 07:08 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 12:40 UTCGHSA enrichment
  16. 2026-08-19 01:32 UTCEG score recompute
  17. 2026-08-19 01:32 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 11:15 UTCGHSA enrichment
  21. 2026-08-17 00:18 UTCEG score recompute
  22. 2026-08-17 00:18 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 13:20 UTCGHSA enrichment
  25. 2026-08-16 02:22 UTCEG score recompute
  26. 2026-08-16 02:22 UTCGHSA enrichment
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 15:25 UTCGHSA enrichment
  29. 2026-08-15 04:27 UTCEG score recompute
  30. 2026-08-15 04:27 UTCGHSA enrichment
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 17:29 UTCGHSA enrichment
  33. 2026-08-14 06:32 UTCEG score recompute
  34. 2026-08-14 06:32 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 19:34 UTCGHSA enrichment
  37. 2026-08-13 08:36 UTCGHSA enrichment
  38. 2026-08-12 21:38 UTCEG score recompute
  39. 2026-08-12 21:38 UTCGHSA enrichment
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 10:41 UTCGHSA enrichment
  42. 2026-08-11 23:43 UTCEG score recompute
  43. 2026-08-11 23:43 UTCGHSA enrichment
  44. 2026-08-11 12:46 UTCGHSA enrichment
  45. 2026-08-11 01:48 UTCEG score recompute
  46. 2026-08-11 01:47 UTCGHSA enrichment
  47. 2026-08-11 00:00 UTCEPSS rescore
  48. 2026-08-10 14:50 UTCGHSA enrichment
  49. 2026-08-10 03:52 UTCGHSA enrichment
  50. 2026-08-09 16:54 UTCEG score recompute
  51. 2026-08-09 16:54 UTCGHSA enrichment
  52. 2026-08-09 13:46 UTCEPSS rescore
  53. 2026-08-09 05:57 UTCGHSA enrichment
  54. 2026-08-08 18:59 UTCEG score recompute
  55. 2026-08-08 18:59 UTCGHSA enrichment
  56. 2026-08-08 16:37 UTCEPSS rescore
  57. 2026-08-08 08:01 UTCGHSA enrichment
  58. 2026-08-07 21:04 UTCEG score recompute
  59. 2026-08-07 21:04 UTCGHSA enrichment
  60. 2026-08-07 10:06 UTCGHSA enrichment
  61. 2026-08-06 23:09 UTCEG score recompute
  62. 2026-08-06 23:09 UTCGHSA enrichment
  63. 2026-08-06 13:47 UTCEPSS rescore
  64. 2026-08-06 11:29 UTCGHSA enrichment
  65. 2026-08-06 00:31 UTCEG score recompute
  66. 2026-08-06 00:31 UTCGHSA enrichment
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-05 13:33 UTCEG score recompute
  69. 2026-08-05 13:33 UTCGHSA enrichment
  70. 2026-08-05 03:44 UTCGHSA enrichment
  71. 2026-08-04 16:46 UTCEG score recompute
  72. 2026-08-04 16:46 UTCGHSA enrichment
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 10:39 UTCEPSS rescore
  75. 2026-08-04 05:48 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 August 5, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 51.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53229?
CVE-2026-53229 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.