# bpf: Do not allow deleting local storage in NMI

CVE record · `CVE-2026-53106`

- **Identifiers:** `CVE-2026-53106`
- **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:30 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: `a10787e6d58c24b51e91c19c6d16c5da89fcaa4b to before e84acaf936970b5b0be2c93bbf255295ba9406df` (git)
  - affected: `a10787e6d58c24b51e91c19c6d16c5da89fcaa4b to before 350de5b8a9befaa2a68861c51f671d4f5f751ca5` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.13`
  - unaffected: `before 5.13` (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 BPF local storage code can deadlock when storage delete helpers run in NMI or reentrant context. The fix makes these helpers return an error when called in NMI, but the source says a reentrant deadlock is still possible. Upgrade to Linux kernel 7.0.10, 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.0014, the 3rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

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

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/e84acaf936970b5b0be2c93bbf255295ba9406df>
- <https://git.kernel.org/stable/c/350de5b8a9befaa2a68861c51f671d4f5f751ca5>

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

---

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