Answer in brief
CVE-2026-98846 records a Unknown severity vulnerability in sctp: check RCV_SHUTDOWN after the sendmsg connect wait. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e8f972b1759d26bbefe4c524caae1ed7c8a593bd || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e701345d886e831fb593a0870d69c8c5de6fc938 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <4f1da630d13de0370e2f6361f961f1c8b384af1c | e8f972b1759d26bbefe4c524caae1ed7c8a593bd, e701345d886e831fb593a0870d69c8c5de6fc938, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669, 4f1da630d13de0370e2f6361f961f1c8b384af1c |
| Linux/Linuxgeneric | 4.16 | Not reported |
| Linux/Linuxgeneric | >=668c9beb9020d5834ee9e43c208190a07d2b1928 <1bef1944ef15a40797305bf916827b04df6307ca || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e8f972b1759d26bbefe4c524caae1ed7c8a593bd || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e701345d886e831fb593a0870d69c8c5de6fc938 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <4f1da630d13de0370e2f6361f961f1c8b384af1c | 1bef1944ef15a40797305bf916827b04df6307ca, e8f972b1759d26bbefe4c524caae1ed7c8a593bd, e701345d886e831fb593a0870d69c8c5de6fc938, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669, 4f1da630d13de0370e2f6361f961f1c8b384af1c |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.