nvme: remove stale namespaces by NSID range during scan
CVE-2026-98056 · published 25 Sept 2026
How serious is it
- Severity: high, CVSS score 7.5 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-98056?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 to < e6a94b2c4c80a38002346ce915a9b9a3d478a3e6, 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 to < c84ad7407fb16b92d9b7a649cc304a9cf3757897, 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 to < f56b2bb4b18b017b056c4c17c66b2c4c54bf6ee4, 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 to < 52200fc41a79da430ccf7c126ed837535b087ea2
- Linux Linux: 4.5
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
nvme: remove stale namespaces by NSID range during scan
nvme_scan_ns_list() drops the stale namespaces in each gap in the
reported NSID list one NSID at a time. Every iteration calls
nvme_find_get_ns() to look the namespace up and removes it if it is
present. The loop runs once per NSID in the gap rather than once per
namespace actually present.
NSIDs are 32-bit, so a target with a sparse NSID space can make a
single gap spin the loop billions of times with nothing to remove.
watchdog: BUG: soft lockup - CPU#4 stuck for 26s!
Workqueue: nvme-wq nvme_scan_work [nvme_core]
RIP: 0010:__srcu_read_unlock+0xb/0x20
Call Trace:
nvme_find_get_ns+0x7d/0xb0 [nvme_core]
nvme_scan_ns_list+0xe8/0x280 [nvme_core]
nvme_scan_work+0x18a/0x280 [nvme_core]
process_one_work+0x197/0x380
worker_thread+0x2fe/0x410
kthread+0xe0/0x100
Rename nvme_remove_invalid_namespaces() to nvme_remove_nsid_range()
and give it an open (start, end) NSID range. ctrl->namespaces is
sorted by NSID, so the whole gap is dropped in a single walk that
stops once end is reached. This bounds the work by the namespaces
that are present instead of by the size of the gap.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/e6a94b2c4c80a38002346ce915a9b9a3d478a3e6
- git.kernel.org/stable/c/c84ad7407fb16b92d9b7a649cc304a9cf3757897
- git.kernel.org/stable/c/f56b2bb4b18b017b056c4c17c66b2c4c54bf6ee4
- git.kernel.org/stable/c/52200fc41a79da430ccf7c126ed837535b087ea2
- git.kernel.org/stable/c/4ed7f3d7d435bf5b63da2814dc9270f5ba896011
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON