In the Linux kernel, the following vulnerability has been resolved: strparser: make sure __strp_recv isn't running before tearing down t…
CVE-2026-99056 · GHSA-cxj6-cg32-r3fc · EUVD-2026-108851 · published 23 Oct 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-99056?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 5.6
- Linux Linux: patch: 7.2.11
- Linux Linux: patch: 7.3
- Linux Linux: patch: 0
- Linux Linux: patch: 6.6.160
- Linux Linux: patch: 6.12.113
- Linux Linux: e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <9f3e9fe1b155e9b4572054d8d140586bc3512ecf
- Linux Linux: e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <0984ebc631792acf8fff105112ee74a6b8f1efcc
- Linux Linux: patch: 6.18.57
- Linux Linux: e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <a18dd388045dc7263d99a07db9de4e0f149ca8f1
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
strparser: make sure __strp_recv isn't running before tearing down the parser
The comment above strp_done() claims that if strp is stopped,
strp_recv will no longer be called. That's only true if the caller has
a mechanism (eg locking) to guarantee that strp_recv() calls that
started before strp_stop() have completed by the time we call
strp_done().
This adds a dummy lock_sock/release_sock pair to guarantee that any
in-flight strp_recv() (which runs under either bh_lock_sock or
lock_sock, depending if it's called from ->sk_data_ready or strp_work)
has completed.
Only espintcp can be affected by this race condition, but this patch
makes sure no future user of strp can have the bug.
This could crash on strp->sk ("general mode" of strp), but this mode
has been here for 9 years and has never been used. It'll be gone soon,
no point worrying about it.
Switch the stopped/paused/etc bits to u8's to avoid races between
strp_stop() and strp_pause/unpause().
A reproducer has been published and turns the possible UAF into an
exploit [1].
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/a18dd388045dc7263d99a07db9de4e0f149ca8f1
- git.kernel.org/stable/c/9f3e9fe1b155e9b4572054d8d140586bc3512ecf
- git.kernel.org/stable/c/d2b5f637b9b67a79a50d42614d10653c13b4e449
- git.kernel.org/stable/c/eaa3a29004c063d7e9d5ea55636f693f67e6db0f
- git.kernel.org/stable/c/0984ebc631792acf8fff105112ee74a6b8f1efcc
- nvd.nist.gov/vuln/detail/CVE-2026-99056
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON