CVE-2026-99597: srcu: Add list_splice_init_srcu()
In the Linux kernel, the following vulnerability has been resolved:
srcu: Add listspliceinitsrcu()
listspliceinitrcu() makes a list look empty to new readers, waits for the current ones with the given sync function, and only then links the entries into the new list. The sync function takes no argument, so it can wait for RCU readers but not for the readers of an srcustruct.
Passing synchronizercu() for a list read under SRCU still builds, but leaves SRCU readers on the entries while the last one's next pointer is moved onto the new list head. nvmeremovenamespaces() does this today.
Add listspliceinitsrcu(), which waits for the readers of the given srcustruct instead.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What conditions are required for this issue to occur?
The affected code must splice a list that is read under SRCU while using list_splice_init_rcu() with synchronize_rcu(). This combination can leave existing SRCU readers accessing list entries after the last entry’s next pointer has been moved to the destination list.
Which kernel path is identified as affected?
The description identifies nvme_remove_namespaces() as currently performing this unsafe operation. The fix adds list_splice_init_srcu(), which waits for readers of the relevant srcu_struct before linking entries into the new list.
What is the appropriate remediation?
Use the kernel update containing list_splice_init_srcu() and the associated conversion for affected SRCU-protected list splices. Code handling lists read under SRCU should wait on the corresponding srcu_struct rather than use synchronize_rcu().