Kernel crash via unsynchronized namespace list splice
Published Nov 20, 2026 · Updated Nov 20, 2026
A race in Linux NVMe namespace removal allows attackers to trigger a kernel page fault via concurrent controller operations. nvme_remove_namespaces() uses list_splice_init_rcu() with synchronize_rcu(), relinking entries before SRCU readers finish and allowing a reader to mistake a stack list head for a namespace. The documented failure requires controller deletion concurrent with Format NVM passthrough waiting for a delayed read on the last namespace; attacker privileges and broader consequences are not established.
Summary
What happened
A race in Linux NVMe namespace removal allows attackers to trigger a kernel page fault via concurrent controller operations. nvme_remove_namespaces() uses list_splice_init_rcu() with synchronize_rcu(), relinking entries before SRCU readers finish and allowing a reader to mistake a stack list head for a namespace. The documented failure requires controller deletion concurrent with Format NVM passthrough waiting for a delayed read on the last namespace; attacker privileges and broader consequences are not established.
The record
- CVE
- CVE-2026-99597
- Published
- Nov 20, 2026
- Updated
- Nov 20, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2026CVE publishedPublication date reported by the CVE source.
- Nov 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.118
- Affected versionversion=0 <6.18.64
- Affected versionversion=0 <7.3.5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2edd46589bf92f71a7c8474d84a7258eb13c2d06
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <89ffb3ea28fef005ae2bd105565c6010dc9deb67
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d06917d0ba226206dbd606330d73a8eb1e3029c1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us