CVE-2026-98846sctp: check RCV_SHUTDOWN after the sendmsg connect wait
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: check RCV_SHUTDOWN after the sendmsg connect wait sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer. Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed. Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 12 days later
· 12 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 7f798168c54455559da0f7a377a23ab7019fec35
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < fe5a23c76fc48b711eb7d6f3462c994e34da36f9
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 1bef1944ef15a40797305bf916827b04df6307ca
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < e8f972b1759d26bbefe4c524caae1ed7c8a593bd
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < e701345d886e831fb593a0870d69c8c5de6fc938
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 4f1da630d13de0370e2f6361f961f1c8b384af1c
- affected 4.16
- unaffected < 4.16
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/7f798168c54455559da0f7a377a23ab7019fec35 (opens in a new tab)
- https://git.kernel.org/stable/c/fe5a23c76fc48b711eb7d6f3462c994e34da36f9 (opens in a new tab)
- https://git.kernel.org/stable/c/1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4 (opens in a new tab)
- https://git.kernel.org/stable/c/1bef1944ef15a40797305bf916827b04df6307ca (opens in a new tab)
- https://git.kernel.org/stable/c/e8f972b1759d26bbefe4c524caae1ed7c8a593bd (opens in a new tab)
- https://git.kernel.org/stable/c/e701345d886e831fb593a0870d69c8c5de6fc938 (opens in a new tab)
- https://git.kernel.org/stable/c/222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 (opens in a new tab)
- https://git.kernel.org/stable/c/4f1da630d13de0370e2f6361f961f1c8b384af1c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103786 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98846)Record last updated .