CVE-2026-99596: Linux kernel · nvme: wait for SRCU readers before splicing the namespace list
Source GCVE Database
Not known to be exploited · fixed in eec7caddb4d152c72a7b6975c6e3f5589cddbdd4 : patch Linux kernel soon.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in eec7caddb4d152c72a7b6975c6e3f5589cddbdd4, a7f566c0c354109ea565ef29afdf23005b2d48dd, 38e604a8271ea9fd4add6669de73cc72da8184ae +2
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: nvme: wait for SRCU readers before splicing the namespace list Readers walk ctrl->namespaces under ctrl->srcu, and some of them sleep there, e.g. nvme_wait_freeze() waiting for I/O to drain. nvme_remove_namespaces() moves the list onto its on-stack ns_list with list_splice_init_rcu(), which only waits for RCU readers before relinking the entries. A reader still on the last namespace then follows its next pointer to ns_list instead of ctrl->namespaces and treats the stack as a namespace. Deleting a controller while a Format NVM passthrough waits for a delayed read on the last namespace gives: BUG: KASAN: stack-out-of-bounds in nvme_wait_freeze+0x102/0x120 Read of size 8 at addr ff110001d2f3fc38 by task nvme/4413 Call Trace: nvme_wait_freeze nvme_passthru_start nvme_submit_user_cmd nvme_user_cmd nvme_dev_ioctl BUG: unable to handle page fault for address: ffffffff8af04850 Use list_splice_init_srcu() instead, which waits for the SRCU readers. This also takes the RCU grace period out of every controller deletion. Deleting 64 tcp controllers with one namespace each, median of 3 runs on each of two boots per kernel: before after nvme disconnect-all (ms) 3491 / 3509 2996 / 3165 nvme_remove_namespaces() avg (ms) 39.0 / 40.5 31.9 / 34.7
References
- nvd.nist.gov/vuln/detail/CVE-2026-99596 (opens in a new tab)
- git.kernel.org/stable/c/38e604a8271ea9fd4add6669de73cc72da8184ae (opens in a new tab)
- git.kernel.org/stable/c/8a0449832b50cd4f99f2d2952cfc1476e5f26d0f (opens in a new tab)
- git.kernel.org/stable/c/a7f566c0c354109ea565ef29afdf23005b2d48dd (opens in a new tab)
- git.kernel.org/stable/c/eec7caddb4d152c72a7b6975c6e3f5589cddbdd4 (opens in a new tab)