CVE-2026-74365

nvdimm/btt: Handle preemption in BTT lane acquisition

HIGH
7.3
CVSS Score
Published: August 15, 2026 at 05:58 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.3
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2577fece583c7c05cda7ad50dde7638c962665e136c75ce3bd299878fd9b238e9803d3817ddafbf34.19.29940ba3fa21250e361bdd8f00800b3e2cb6160de955.10.2015.15.1395.4.2616.1.636.5.126.6.26.766eb7b7f23dd9aec5356e7054dd3596ae7648ff56f50b414f1a0d790f11a6438a3ad6d0577eb2c18b0e7a935739f33ed2bd6868b89f97dd4c2683c26b27751fb1f271bbb78d5993c0b10011628e40e18f23859748e3d530217b197e146a9ac84faf0a282
Vendor states this is fixed in 417918783bcfe0be135019df16a267b3af442efd (fixed)
Vendor states this is fixed in 4eafa810b042d985ec6bbf5b514414e73cee6f6f (fixed)
Vendor states this is fixed in 5c53406098b599c420b031e6ec5ba8a2f3794c50 (fixed)
Vendor states this is fixed in 73e35c1bdfa160b41fdbe204e02325f0687de506 (fixed)
Vendor states this is fixed in 8d4b989d9c9afe5f185aa5853b666fc4617afe9e (fixed)
Vendor states this is fixed in fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.3HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card