Skip to content
Threat Brief

← All advisories

CVE-2026-99596

Severity unknownNo known exploitationFix available

nvme: wait for SRCU readers before splicing the namespace list

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 6.6.48 before 6.76.7CVE Program
LinuxLinuxfrom be647e2c76b27f409cdd520f66c95be888b553a3 before 38e604a8271ea9fd4add6669de73cc72da8184ae38e604a8271ea9fd4add6669de73cc72da8184aeCVE Program
LinuxLinuxfrom be647e2c76b27f409cdd520f66c95be888b553a3 before eec7caddb4d152c72a7b6975c6e3f5589cddbdd4eec7caddb4d152c72a7b6975c6e3f5589cddbdd4CVE Program
LinuxLinuxfrom be647e2c76b27f409cdd520f66c95be888b553a3 before 8a0449832b50cd4f99f2d2952cfc1476e5f26d0f8a0449832b50cd4f99f2d2952cfc1476e5f26d0fCVE Program
LinuxLinuxfrom be647e2c76b27f409cdd520f66c95be888b553a3 before a7f566c0c354109ea565ef29afdf23005b2d48dda7f566c0c354109ea565ef29afdf23005b2d48ddCVE Program
LinuxLinux6.10Not documentedCVE Program
LinuxLinux82f20194bf46d4393fb2c4337e1effbbbe95d9b9Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.10Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references