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 — Patch released 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

July 22, 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(3)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu
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.

Weakness Classification(3)

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

Additional Vendor Advisories

(5)

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 13× in last 7d / 81× 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-27 06:10 UTCVendor advisory
  2. 2026-07-27 06:10 UTCGHSA enrichment
  3. 2026-07-26 15:39 UTCEG score recompute
  4. 2026-07-26 15:39 UTCVendor advisory
  5. 2026-07-26 15:39 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 00:12 UTCGHSA enrichment
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-16 11:35 UTCGHSA enrichment
  21. 2026-07-15 22:55 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 10:18 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 60 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 21:33 UTCGHSA enrichment
  3. 2026-07-14 08:56 UTCGHSA enrichment
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 20:19 UTCGHSA enrichment
  6. 2026-07-13 07:42 UTCGHSA enrichment
  7. 2026-07-12 19:05 UTCGHSA enrichment
  8. 2026-07-12 06:27 UTCGHSA enrichment
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 17:50 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 05:12 UTCGHSA enrichment
  14. 2026-07-10 16:32 UTCGHSA enrichment
  15. 2026-07-10 03:53 UTCGHSA enrichment
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 15:13 UTCGHSA enrichment
  19. 2026-07-09 02:31 UTCGHSA enrichment
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 13:54 UTCGHSA enrichment
  23. 2026-07-08 01:12 UTCGHSA enrichment
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 12:35 UTCGHSA enrichment
  27. 2026-07-06 23:58 UTCGHSA enrichment
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 11:21 UTCGHSA enrichment
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-05 22:17 UTCGHSA enrichment
  34. 2026-07-05 09:40 UTCGHSA enrichment
  35. 2026-07-05 02:31 UTCEPSS rescore
  36. 2026-07-05 02:30 UTCEPSS rescore
  37. 2026-07-04 21:03 UTCGHSA enrichment
  38. 2026-07-04 08:26 UTCGHSA enrichment
  39. 2026-07-04 06:31 UTCEPSS rescore
  40. 2026-07-03 19:48 UTCGHSA enrichment
  41. 2026-07-03 07:11 UTCGHSA enrichment
  42. 2026-07-02 18:33 UTCGHSA enrichment
  43. 2026-07-02 05:55 UTCGHSA enrichment
  44. 2026-07-01 17:16 UTCGHSA enrichment
  45. 2026-07-01 15:07 UTCEPSS rescore
  46. 2026-07-01 04:38 UTCGHSA enrichment
  47. 2026-06-30 23:22 UTCEPSS rescore
  48. 2026-06-30 16:01 UTCEG score recompute▲ 7.80
  49. 2026-06-30 16:00 UTCGHSA enrichment
  50. 2026-06-29 14:06 UTCEPSS rescore
  51. 2026-06-29 14:06 UTCEPSS rescore
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-28 04:56 UTCEPSS rescore
  56. 2026-06-27 17:10 UTCGHSA enrichment
  57. 2026-06-27 03:08 UTCEPSS rescore
  58. 2026-06-25 13:49 UTCEPSS rescore
  59. 2026-06-24 18:23 UTCEG score recompute
  60. 2026-06-24 18:02 UTCNVD updatefirst tracked

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 July 22, 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

Explore the affected products and dependency analysis for 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