CVE-2026-74365

High

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.

SeverityHigh
CVSS7.3
Exploit probability—
ProductLinux
PublishedAug 15, 2026
First seenAug 15, 2026

How to fix

Update
  • Linux Linuxfd7a97b2514cfc4b4cc067a27dd39bde2a8b1735, 73e35c1bdfa160b41fdbe204e02325f0687de506, 417918783bcfe0be135019df16a267b3af442efd, 5c53406098b599c420b031e6ec5ba8a2f3794c50, 4eafa810b042d985ec6bbf5b514414e73cee6f6f, 8d4b989d9c9afe5f185aa5853b666fc4617afe9e, 6.1.178, 6.6.145, 4.20, 5.5, 5.11, 5.16, 6.6 or later

Affected products

ProductAffected versionsFixed in
Linux Linuxf23859748e3d530217b197e146a9ac84faf0a282 ≤ v < fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735, 6f50b414f1a0d790f11a6438a3ad6d0577eb2c18 ≤ v < 73e35c1bdfa160b41fdbe204e02325f0687de506, 36c75ce3bd299878fd9b238e9803d3817ddafbf3 ≤ v < 417918783bcfe0be135019df16a267b3af442efd, 36c75ce3bd299878fd9b238e9803d3817ddafbf3 ≤ v < 5c53406098b599c420b031e6ec5ba8a2f3794c50, 36c75ce3bd299878fd9b238e9803d3817ddafbf3 ≤ v < 4eafa810b042d985ec6bbf5b514414e73cee6f6f, 36c75ce3bd299878fd9b238e9803d3817ddafbf3 ≤ v < 8d4b989d9c9afe5f185aa5853b666fc4617afe9e, 2577fece583c7c05cda7ad50dde7638c962665e1, 40ba3fa21250e361bdd8f00800b3e2cb6160de95, b0e7a935739f33ed2bd6868b89f97dd4c2683c26, 66eb7b7f23dd9aec5356e7054dd3596ae7648ff5, b27751fb1f271bbb78d5993c0b10011628e40e18, 6.1.63 ≤ v < 6.1.178, 6.6.2 ≤ v < 6.6.145, 4.19.299 ≤ v < 4.20, 5.4.261 ≤ v < 5.5, 5.10.201 ≤ v < 5.11, 5.15.139 ≤ v < 5.16, 6.5.12 ≤ v < 6.6, 6.7fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735, 73e35c1bdfa160b41fdbe204e02325f0687de506, 417918783bcfe0be135019df16a267b3af442efd, 5c53406098b599c420b031e6ec5ba8a2f3794c50, 4eafa810b042d985ec6bbf5b514414e73cee6f6f, 8d4b989d9c9afe5f185aa5853b666fc4617afe9e, 6.1.178, 6.6.145, 4.20, 5.5, 5.11, 5.16, 6.6

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.