# ice: fix race condition in TX timestamp ring cleanup

CVE record · `CVE-2026-53008`

- **Identifiers:** `CVE-2026-53008`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Jun 2026, 16:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ccde82e909467abdf098a8ee6f63e1ecf9a47ce5 to before e98cea6d5562f546482fab8ad571e95e3fff1800` (git)
  - affected: `ccde82e909467abdf098a8ee6f63e1ecf9a47ce5 to before 097409d20465723283632515df73038a4a853eda` (git)
  - affected: `ccde82e909467abdf098a8ee6f63e1ecf9a47ce5 to before 7c72ec18c2a4111204c2e915f8e4f6d849ce9398` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.18`
  - unaffected: `before 6.18` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.10 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The ice network driver in the Linux kernel has a race condition in TX timestamp ring cleanup that can cause a NULL pointer dereference when a transmit runs on another CPU while the ring is being freed. The source gives few details on what access an attacker needs or what they can do beyond the crash. Upgrade the Linux kernel to 6.18.57 or later in the 6.18 series, 7.0.10 or later in the 7.0 series, or 7.1 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jun 2026, 16:29 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53008)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53008)

## Sources

- [CVE List: CVE-2026-53008](https://www.cve.org/CVERecord?id=CVE-2026-53008)
- [NVD: CVE-2026-53008](https://nvd.nist.gov/vuln/detail/CVE-2026-53008)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53008>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53008/>. Everything for agents: <https://agentprime.io/llms.txt>.
