# ice: fix potential NULL pointer deref in error path of ice_set_ringparam()

CVE record · `CVE-2026-53007`

- **Identifiers:** `CVE-2026-53007`
- **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 c789649d4334a3767210071311d58bc8e74bdec1` (git)
  - affected: `ccde82e909467abdf098a8ee6f63e1ecf9a47ce5 to before c54e3c270384829336b2526033d44ce1aa6dc67c` (git)
  - affected: `ccde82e909467abdf098a8ee6f63e1ecf9a47ce5 to before fa28351f970fa5138c7c5dedfe5dea480a0ee065` (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 Linux kernel ice driver's error path in ice_set_ringparam() can cause a NULL pointer dereference when a ring setup fails after the TXTIME flag is set. The source gives few details on what an attacker would need to trigger it. Upgrade to Linux kernel 6.18.57, 7.0.10, 7.1 or later. No workaround is listed.

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.0016, the 5th 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-53007)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53007)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/c789649d4334a3767210071311d58bc8e74bdec1>
- <https://git.kernel.org/stable/c/c54e3c270384829336b2526033d44ce1aa6dc67c>
- <https://git.kernel.org/stable/c/fa28351f970fa5138c7c5dedfe5dea480a0ee065>

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-53007>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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