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

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- 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). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.19%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

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

## References

- https://git.kernel.org/stable/c/89ffb3ea28fef005ae2bd105565c6010dc9deb67 (CNA: Linux)

- https://git.kernel.org/stable/c/2edd46589bf92f71a7c8474d84a7258eb13c2d06 (CNA: Linux)

- https://git.kernel.org/stable/c/b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b (CNA: Linux)

- https://git.kernel.org/stable/c/d06917d0ba226206dbd606330d73a8eb1e3029c1 (CNA: Linux)

- https://git.kernel.org/stable/c/2edd46589bf92f71a7c8474d84a7258eb13c2d06 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/89ffb3ea28fef005ae2bd105565c6010dc9deb67 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/d06917d0ba226206dbd606330d73a8eb1e3029c1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99597; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99597; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99597; retrieved 2026-11-22; source updated Not reported

Revision: 6e51b9816a7c63b0be5599973120fb7a920ae9fe34bc14043da5a4cf1cc81186

Canonical: https://y2.dev/cve/CVE-2026-99597

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.