Live › vulnerability › CVE-2026-98846
Go to dashboardA race in the Linux kernel's SCTP sendmsg path lets a concurrent ABORT and shutdown(SHUT_RD) free an association while sendmsg still uses it. The sources do not state the attacker's full capability beyond a use-after-free in the kernel.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with SCTP support that the fix covers; the race needs concurrent socket use of SCTP connections. Hosts that do not use SCTP can skip it, though the sources do not say whether SCTP must be loaded or reachable for exposure.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel builds listed in the NVD entrylsmod | grep sctp to see whether the SCTP module is loaded at allecho 'install sctp /bin/false' > /etc/modprobe.d/sctp.confEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98846")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.