CVE-2026-53008

MEDIUMNVD 4.74.7—
EchelonGraph scoreHIGH confidence

Score 4.7 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: 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 race condition in TX timestamp ring cleanup

Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointer dereference.

ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map call on another CPU to dereference the tstamp_ring, which could lead to a NULL pointer dereference.

CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map() --------------------------------|--------------------------------- tx_ring->tstamp_ring = NULL | | ice_is_txtime_cfg() -> true | tstamp_ring = tx_ring->tstamp_ring | tstamp_ring->count // NULL deref! flags &= ~ICE_TX_FLAGS_TXTIME |

Fix by:

  • Reordering ice_free_tx_tstamp_ring() to clear the flag before
NULLing the pointer, with smp_wmb() to ensure proper ordering.
  • Adding smp_rmb() in ice_tx_map() after the flag check to order the
flag read before the pointer read, using READ_ONCE() for the pointer, and adding a NULL check as a safety net.
  • Converting tx_ring->flags from u8 to DECLARE_BITMAP() and using
atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag operations throughout the driver:
  • ICE_TX_RING_FLAGS_XDP
  • ICE_TX_RING_FLAGS_VLAN_L2TAG1
  • ICE_TX_RING_FLAGS_VLAN_L2TAG2
  • ICE_TX_RING_FLAGS_TXTIME

CVSS v3
4.7
EG Score
4.7(high)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
No patch confirmed yet.
generic

ice: fix race condition in TX timestamp ring cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

ice: fix race condition in TX timestamp ring cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/097409d20465723283632515df73038a4a853eda

Vendor Advisories for CVE-2026-53008(1)

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 4× in last 7d / 44× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-19 02:29 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-17 04:17 UTCGHSA enrichment
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 03:16 UTCGHSA enrichment
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:14 UTCEG score recompute▲ 4.70
  12. 2026-07-15 02:14 UTCGHSA enrichment
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 19:21 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-12 04:35 UTCGHSA enrichment
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 06:56 UTCGHSA enrichment
Show 22 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 09:16 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 11:25 UTCGHSA enrichment
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 13:40 UTCGHSA enrichment
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 16:02 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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53008?
CVE-2026-53008 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ice: fix race condition in TX timestamp ring cleanup Fix a race condition between icefreetxtstampring() and icetxmap() that can cause a NULL pointer dereference. icefreetxtstampring currently clears the ICETXFLAGS_TXTIME flag after…
When was CVE-2026-53008 disclosed?
CVE-2026-53008 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53008 actively exploited?
CVE-2026-53008 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53008?
CVE-2026-53008 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-53008?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53008, 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-53008

Explore →

Is Your Infrastructure Affected by CVE-2026-53008?

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

Start Free Scan →Browse All CVEs