Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74365, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
NVDNVD · Received3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected f23859748e3d530217b197e146a9ac84faf0a282 – < fd7a97b2514cfc4b4cc067a27dd39bde2a8b1735
    • affected 6f50b414f1a0d790f11a6438a3ad6d0577eb2c18 – < 73e35c1bdfa160b41fdbe204e02325f0687de506
    • affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 – < 417918783bcfe0be135019df16a267b3af442efd
    • affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 – < 5c53406098b599c420b031e6ec5ba8a2f3794c50
    • affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 – < 4eafa810b042d985ec6bbf5b514414e73cee6f6f
    • affected 36c75ce3bd299878fd9b238e9803d3817ddafbf3 – < 8d4b989d9c9afe5f185aa5853b666fc4617afe9e
    • affected 2577fece583c7c05cda7ad50dde7638c962665e1
    • affected 40ba3fa21250e361bdd8f00800b3e2cb6160de95
    • affected b0e7a935739f33ed2bd6868b89f97dd4c2683c26
    • affected 66eb7b7f23dd9aec5356e7054dd3596ae7648ff5
    • affected b27751fb1f271bbb78d5993c0b10011628e40e18
    • affected 6.1.63 – < 6.1.178
    • affected 6.6.2 – < 6.6.145
    • affected 4.19.299 – < 4.20
    • affected 5.4.261 – < 5.5
    • affected 5.10.201 – < 5.11
    • affected 5.15.139 – < 5.16
    • affected 6.5.12 – < 6.6
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74365 badge
[![CVE-2026-74365](https://cveledger.app/badge/CVE-2026-74365.svg)](https://cveledger.app/cve/CVE-2026-74365)

Record last updated .