CVE-2026-74365: nvdimm/btt: Handle preemption in BTT lane acquisition
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4.20, 417918783bcfe0be135019df16a267b3af442efd, 4eafa810b042d985ec6bbf5b514414e73cee6f6f.
Low priority for now. Upgrade to Linux Linux 4.20, 417918783bcfe0be135019df16a267b3af442efd, 4eafa810b042d985ec6bbf5b514414e73cee6f6f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2577fece583c7c05cda7ad50dde7638c962665e1, 40ba3fa21250e361bdd8f00800b3e2cb6160de95, b0e7a935739f33ed2bd6868b89f97dd4c2683c26, 66eb7b7f23dd9aec5356e7054dd3596ae7648ff5, b27751fb1f271bbb78d5993c0b10011628e40e18, 6.7affected
- f23859748e3d530217b197e146a9ac84faf0a282 and later · before fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735affected · git
- 6f50b414f1a0d790f11a6438a3ad6d0577eb2c18 and later · before 73e35c1bdfa160b41fdbe204e02325f0687de506affected · git
- 36c75ce3bd299878fd9b238e9803d3817ddafbf3 and later · before 417918783bcfe0be135019df16a267b3af442efdaffected · git
- 36c75ce3bd299878fd9b238e9803d3817ddafbf3 and later · before 5c53406098b599c420b031e6ec5ba8a2f3794c50affected · git
- 36c75ce3bd299878fd9b238e9803d3817ddafbf3 and later · before 4eafa810b042d985ec6bbf5b514414e73cee6f6faffected · git
- 36c75ce3bd299878fd9b238e9803d3817ddafbf3 and later · before 8d4b989d9c9afe5f185aa5853b666fc4617afe9eaffected · git
- 6.1.63 and later · before 6.1.178affected · semver
- 6.6.2 and later · before 6.6.145affected · semver
- 4.19.299 and later · before 4.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74361Aug 15, 2026 · nvme: fix FDP fdpcidx bounds check39Monitor
- ← EarlierCVE-2026-74363Aug 15, 2026 · bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs31Monitor
- Later →CVE-2026-74367Aug 15, 2026 · wifi: ath12k: fix inconsistent arvif state in vdev_create error paths31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 417918783bcfe0be135019df16a267b3af442efd | Vendor (CNA) |
| Linux Linux | 4eafa810b042d985ec6bbf5b514414e73cee6f6f | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5c53406098b599c420b031e6ec5ba8a2f3794c50 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.6 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 73e35c1bdfa160b41fdbe204e02325f0687de506 | Vendor (CNA) |
| Linux Linux | 8d4b989d9c9afe5f185aa5853b666fc4617afe9e | Vendor (CNA) |
| Linux Linux | fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4eafa810b042d985ec6bbf5b514414e73cee6f6f
- git.kernel.org/stable/c/5c53406098b599c420b031e6ec5ba8a2f3794c50
- git.kernel.org/stable/c/73e35c1bdfa160b41fdbe204e02325f0687de506
- git.kernel.org/stable/c/8d4b989d9c9afe5f185aa5853b666fc4617afe9e
- git.kernel.org/stable/c/fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735
Vendor advisories and official records. Exploit/PoC links are deliberately left out.