CVE-2026-99596

published 20 Nov 2026 · updated 20 Nov 2026

nvme: wait for SRCU readers before splicing the namespace list

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel eec7caddb4d152c72a7b6975c6e3f5589cddbdd4, Kernel 6.7, Kernel 38e604a8271ea9fd4add6669de73cc72da8184ae and 5 more.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=be647e2c76b27f409cdd520f66c95be888b553a3 <eec7caddb4d152c72a7b6975c6e3f5589cddbdd4, >=6.6.48 <6.7, >=be647e2c76b27f409cdd520f66c95be888b553a3 <38e604a8271ea9fd4add6669de73cc72da8184ae, >=be647e2c76b27f409cdd520f66c95be888b553a3 <8a0449832b50cd4f99f2d2952cfc1476e5f26d0f, >=be647e2c76b27f409cdd520f66c95be888b553a3 <a7f566c0c354109ea565ef29afdf23005b2d48dd, =6.10, =82f20194bf46d4393fb2c4337e1effbbbe95d9b9eec7caddb4d152c72a7b6975c6e3f5589cddbdd4, 6.7, 38e604a8271ea9fd4add6669de73cc72da8184ae, 8a0449832b50cd4f99f2d2952cfc1476e5f26d0f, a7f566c0c354109ea565ef29afdf23005b2d48dd
linux-kernel: Kernel>=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=6.6.48 <6.7, >=6.10.0 <6.12.1186.18.64, 7.3.5, 6.7, 6.12.118

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99596 severity on Zeptric[![CVE-2026-99596](https://zeptric.io/badge/cve/CVE-2026-99596.svg)](https://zeptric.io/cve/CVE-2026-99596)