CVE-2026-99597: srcu: Add list_splice_init_srcu()

Published Nov 20, 2026
·
Updated

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

7 affected componentsFixes available
linux/kernel<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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().

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203