CVE-2026-99056: Linux kernel · strparser: make sure __strp_recv isn't running before tearing down the parser
Source GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in eaa3a29004c063d7e9d5ea55636f693f67e6db0f : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in eaa3a29004c063d7e9d5ea55636f693f67e6db0f, d2b5f637b9b67a79a50d42614d10653c13b4e449, a18dd388045dc7263d99a07db9de4e0f149ca8f1 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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].
References
- nvd.nist.gov/vuln/detail/CVE-2026-99056 (opens in a new tab)
- git.kernel.org/stable/c/0984ebc631792acf8fff105112ee74a6b8f1efcc (opens in a new tab)
- git.kernel.org/stable/c/9f3e9fe1b155e9b4572054d8d140586bc3512ecf (opens in a new tab)
- git.kernel.org/stable/c/a18dd388045dc7263d99a07db9de4e0f149ca8f1 (opens in a new tab)
- git.kernel.org/stable/c/d2b5f637b9b67a79a50d42614d10653c13b4e449 (opens in a new tab)
- git.kernel.org/stable/c/eaa3a29004c063d7e9d5ea55636f693f67e6db0f (opens in a new tab)