Public vulnerability disclosure

CVE-2026-99597

srcu: Add list_splice_init_srcu()

published

In the Linux kernel, the following vulnerability has been resolved: srcu: Add list_splice_init_srcu() list_splice_init_rcu() 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 srcu_struct. Passing synchronize_rcu() 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. nvme_remove_namespaces() does this today. Add list_splice_init_srcu(), which waits for the readers of the given srcu_struct instead.

Technical severityUnscoredNo score in collected sources
Published2026-11-20Source updated 2026-11-22
Collected2026-11-223 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ be647e2c76b27f409cdd520f66c95be888b553a3; < 89ffb3ea28fef005ae2bd105565c6010dc9deb67 (affected, git)
≥ be647e2c76b27f409cdd520f66c95be888b553a3; < 2edd46589bf92f71a7c8474d84a7258eb13c2d06 (affected, git)
≥ be647e2c76b27f409cdd520f66c95be888b553a3; < b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b (affected, git)
≥ be647e2c76b27f409cdd520f66c95be888b553a3; < d06917d0ba226206dbd606330d73a8eb1e3029c1 (affected, git)
82f20194bf46d4393fb2c4337e1effbbbe95d9b9 (affected, git)
≥ 6.6.48; < 6.7 (affected, semver)
Other versions: unaffected
CNA: Linux
Linux
Linux
6.10 (affected)
≥ 0; < 6.10 (unaffected, semver)
≥ 6.12.118; ≤ 6.12.* (unaffected, semver)
≥ 6.18.64; ≤ 6.18.* (unaffected, semver)
≥ 7.3.5; ≤ 7.3.* (unaffected, semver)
≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide