nvdimm/btt: Handle preemption in BTT lane acquisition
Summary
| CVE | CVE-2026-74365 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:38 UTC |
| Updated | 2026-08-15 06:22:38 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected f23859748e3d530217b197e146a9ac84faf0a282 fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6f50b414f1a0d790f11a6438a3ad6d0577eb2c18 73e35c1bdfa160b41fdbe204e02325f0687de506 git |
Not specified |
| CNA |
Linux |
Linux |
affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 417918783bcfe0be135019df16a267b3af442efd git |
Not specified |
| CNA |
Linux |
Linux |
affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 5c53406098b599c420b031e6ec5ba8a2f3794c50 git |
Not specified |
| CNA |
Linux |
Linux |
affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 4eafa810b042d985ec6bbf5b514414e73cee6f6f git |
Not specified |
| CNA |
Linux |
Linux |
affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 8d4b989d9c9afe5f185aa5853b666fc4617afe9e git |
Not specified |
| CNA |
Linux |
Linux |
affected 2577fece583c7c05cda7ad50dde7638c962665e1 git |
Not specified |
| CNA |
Linux |
Linux |
affected 40ba3fa21250e361bdd8f00800b3e2cb6160de95 git |
Not specified |
| CNA |
Linux |
Linux |
affected b0e7a935739f33ed2bd6868b89f97dd4c2683c26 git |
Not specified |
| CNA |
Linux |
Linux |
affected 66eb7b7f23dd9aec5356e7054dd3596ae7648ff5 git |
Not specified |
| CNA |
Linux |
Linux |
affected b27751fb1f271bbb78d5993c0b10011628e40e18 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1.63 6.1.178 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6.2 6.6.145 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 4.19.299 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.4.261 5.5 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.10.201 5.11 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15.139 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.5.12 6.6 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.7 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.7 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/5c53406098b599c420b031e6ec5ba8a2f3794c50 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/417918783bcfe0be135019df16a267b3af442efd |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4eafa810b042d985ec6bbf5b514414e73cee6f6f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/73e35c1bdfa160b41fdbe204e02325f0687de506 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8d4b989d9c9afe5f185aa5853b666fc4617afe9e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.