CVE-2026-53009

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ice: fix double-free of tx_buf skb

If ice_tso() or ice_tx_csum() fail, the error path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains unchanged, so the potential problem will likely fix itself when the next packet is transmitted and the tx_buf gets overwritten. But if there is no next packet and the interface is brought down instead, ice_clean_tx_ring() -> ice_unmap_and_free_tx_buf() will find the tx_buf and free the skb for the second time.

The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY in the error path, so that ice_unmap_and_free_tx_buf(). Move the initialization of 'first' up, to ensure it's already valid in case we hit the linearization error path.

The bug was spotted by AI while I had it looking for something else. It also proposed an initial version of the patch.

I reproduced the bug and tested the fix by adding code to inject failures, on a build with KASAN.

I looked for similar bugs in related Intel drivers and did not find any.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 12, 2026

Advisory Details (2)

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

ice: fix double-free of tx_buf skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c08fc2119ef0281cfa2cee007acf0a251be55f2
generic

ice: fix double-free of tx_buf skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a303baa715e6b78d6a406aaf335f87ff35acfcd

Vendor Advisories for CVE-2026-53009(5)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-20ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-20ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-20ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-20ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-20ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-20ubuntu
redhatkernel-0:4.18.0-553.155.1.el8_102026-08-12redhat
redhatkernel-rt-0:4.18.0-553.155.1.rt7.496.el8_102026-08-12redhat
redhatkernel-0:6.12.0-211.37.1.el10_22026-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

Weakness Classification(3)

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

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 32× in last 7d / 148× 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 222 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:06 UTCVendor advisory
  3. 2026-08-20 20:06 UTCGHSA enrichment
  4. 2026-08-20 07:28 UTCEG score recompute
  5. 2026-08-20 07:28 UTCVendor advisory
  6. 2026-08-20 07:28 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:52 UTCVendor advisory
  9. 2026-08-19 14:51 UTCGHSA enrichment
  10. 2026-08-19 02:10 UTCEG score recompute
  11. 2026-08-19 02:10 UTCVendor advisory
  12. 2026-08-19 02:10 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 07:08 UTCVendor advisory
  16. 2026-08-17 07:08 UTCGHSA enrichment
  17. 2026-08-16 18:31 UTCEG score recompute
  18. 2026-08-16 18:31 UTCVendor advisory
  19. 2026-08-16 18:31 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:56 UTCEG score recompute
  22. 2026-08-16 04:56 UTCVendor advisory
  23. 2026-08-16 04:56 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 16:19 UTCVendor advisory
Show 75 more
  1. 2026-08-15 16:19 UTCGHSA enrichment
  2. 2026-08-15 03:42 UTCEG score recompute
  3. 2026-08-15 03:42 UTCVendor advisory
  4. 2026-08-15 03:42 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 15:04 UTCVendor advisory
  7. 2026-08-14 15:04 UTCGHSA enrichment
  8. 2026-08-14 02:27 UTCEG score recompute
  9. 2026-08-14 02:27 UTCVendor advisory
  10. 2026-08-14 02:27 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 13:50 UTCVendor advisory
  13. 2026-08-13 13:50 UTCGHSA enrichment
  14. 2026-08-13 01:13 UTCEG score recompute
  15. 2026-08-13 01:13 UTCVendor advisory
  16. 2026-08-13 01:13 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 12:36 UTCEG score recompute
  19. 2026-08-12 12:36 UTCVendor advisory
  20. 2026-08-12 12:36 UTCGHSA enrichment
  21. 2026-08-12 12:11 UTCVendor advisory
  22. 2026-08-12 12:11 UTCGHSA enrichment
  23. 2026-08-12 09:43 UTCVendor advisory
  24. 2026-08-12 09:43 UTCGHSA enrichment
  25. 2026-08-11 21:05 UTCEG score recompute
  26. 2026-08-11 21:05 UTCVendor advisory
  27. 2026-08-11 21:05 UTCGHSA enrichment
  28. 2026-08-11 08:28 UTCEG score recompute
  29. 2026-08-11 08:28 UTCVendor advisory
  30. 2026-08-11 08:28 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 19:51 UTCVendor advisory
  33. 2026-08-10 19:51 UTCGHSA enrichment
  34. 2026-08-10 07:13 UTCVendor advisory
  35. 2026-08-10 07:13 UTCGHSA enrichment
  36. 2026-08-09 18:37 UTCEG score recompute
  37. 2026-08-09 18:37 UTCVendor advisory
  38. 2026-08-09 18:37 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 06:00 UTCVendor advisory
  41. 2026-08-09 06:00 UTCGHSA enrichment
  42. 2026-08-08 17:23 UTCEG score recompute
  43. 2026-08-08 17:23 UTCVendor advisory
  44. 2026-08-08 17:23 UTCGHSA enrichment
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 04:45 UTCEG score recompute
  47. 2026-08-08 04:45 UTCVendor advisory
  48. 2026-08-08 04:45 UTCGHSA enrichment
  49. 2026-08-07 16:08 UTCVendor advisory
  50. 2026-08-07 16:08 UTCGHSA enrichment
  51. 2026-08-07 03:31 UTCVendor advisory
  52. 2026-08-07 03:31 UTCGHSA enrichment
  53. 2026-08-06 14:54 UTCEG score recompute
  54. 2026-08-06 14:54 UTCVendor advisory
  55. 2026-08-06 14:54 UTCGHSA enrichment
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-06 02:13 UTCEG score recompute
  58. 2026-08-06 02:13 UTCVendor advisory
  59. 2026-08-06 02:13 UTCGHSA enrichment
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 13:36 UTCEG score recompute
  62. 2026-08-05 13:36 UTCVendor advisory
  63. 2026-08-05 13:36 UTCGHSA enrichment
  64. 2026-08-05 03:48 UTCVendor advisory
  65. 2026-08-05 03:48 UTCGHSA enrichment
  66. 2026-08-04 15:11 UTCEG score recompute
  67. 2026-08-04 15:11 UTCVendor advisory
  68. 2026-08-04 15:11 UTCGHSA enrichment
  69. 2026-08-04 15:10 UTCEPSS rescore
  70. 2026-08-04 10:39 UTCEPSS rescore
  71. 2026-08-03 20:35 UTCEG score recompute
  72. 2026-08-03 20:35 UTCVendor advisory
  73. 2026-08-03 20:35 UTCGHSA enrichment
  74. 2026-08-03 10:36 UTCEPSS rescore
  75. 2026-08-03 07:57 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53009?
CVE-2026-53009 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ice: fix double-free of tx_buf skb If icetso() or icetx_csum() fail, the error path in icexmitframering() frees the skb, but the 'first' txbuf still points to it and is marked as valid (ICETXBUF_SKB). 'nexttouse' remains unchanged,…
When was CVE-2026-53009 disclosed?
CVE-2026-53009 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53009 actively exploited?
CVE-2026-53009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53009?
CVE-2026-53009 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53009, 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-53009

Explore →

Is Your Infrastructure Affected by CVE-2026-53009?

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

Start Free Scan →Browse All CVEs