CVE-2026-98846: Linux kernel · sctp: check RCV_SHUTDOWN after the sendmsg connect wait
Source GCVE Database
Not known to be exploited · fixed in e701345d886e831fb593a0870d69c8c5de6fc938 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e701345d886e831fb593a0870d69c8c5de6fc938, e8f972b1759d26bbefe4c524caae1ed7c8a593bd, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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– |
AI-suggested
A fix has been implemented in the Linux kernel to check the RCV_SHUTDOWN flag appropriately in sctp_sendmsg_to_asoc(), preventing use-after-free. Users should apply the official kernel update that includes this fix once available. No additional mitigation is required as the fix preserves existing behavior for connect() callers.
Description
A vulnerability in the Linux kernel SCTP implementation was resolved that could lead to use-after-free conditions due to improper checking of socket shutdown state after a sendmsg connect wait. The issue involves sctp_wait_for_connect() dropping the socket lock while sleeping, allowing concurrent shutdowns to cause dangling pointer dereferences in sctp_sendmsg_to_asoc().
References
- nvd.nist.gov/vuln/detail/CVE-2026-98846 (opens in a new tab)
- git.kernel.org/stable/c/222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 (opens in a new tab)
- git.kernel.org/stable/c/4f1da630d13de0370e2f6361f961f1c8b384af1c (opens in a new tab)
- git.kernel.org/stable/c/e701345d886e831fb593a0870d69c8c5de6fc938 (opens in a new tab)
- git.kernel.org/stable/c/e8f972b1759d26bbefe4c524caae1ed7c8a593bd (opens in a new tab)
- git.kernel.org/stable/c/1bef1944ef15a40797305bf916827b04df6307ca (opens in a new tab)