CVE-2026-53009

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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 — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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:

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(high)
EPSS
2.4%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 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(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 35× in last 7d / 47× 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-06 23:58 UTCEG score recompute
  2. 2026-07-06 23:58 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:21 UTCEG score recompute
  6. 2026-07-06 11:21 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 22:17 UTCEG score recompute
  10. 2026-07-05 22:17 UTCGHSA enrichment
  11. 2026-07-05 09:40 UTCEG score recompute
  12. 2026-07-05 09:40 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 21:03 UTCEG score recompute
  16. 2026-07-04 21:03 UTCGHSA enrichment
  17. 2026-07-04 08:26 UTCEG score recompute
  18. 2026-07-04 08:26 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 19:48 UTCEG score recompute
  21. 2026-07-03 19:48 UTCGHSA enrichment
  22. 2026-07-03 07:11 UTCEG score recompute
  23. 2026-07-03 07:11 UTCGHSA enrichment
  24. 2026-07-02 18:33 UTCEG score recompute
  25. 2026-07-02 18:33 UTCGHSA enrichment
Show 22 more
  1. 2026-07-02 05:55 UTCEG score recompute
  2. 2026-07-02 05:55 UTCGHSA enrichment
  3. 2026-07-01 17:16 UTCEG score recompute
  4. 2026-07-01 17:16 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 04:38 UTCEG score recompute
  7. 2026-07-01 04:38 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 16:01 UTCEG score recompute▲ 7.80
  10. 2026-06-30 16:00 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 17:10 UTCEG score recompute
  18. 2026-06-27 17:10 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 18:23 UTCEG score recompute
  22. 2026-06-24 18:02 UTCNVD updatefirst tracked

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 June 30, 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 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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