sctp: check RCV_SHUTDOWN after the sendmsg connect wait
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1bef1944ef15a40797305bf916827b04df6307ca, Kernel 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4, Kernel 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.16, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <1bef1944ef15a40797305bf916827b04df6307ca, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <4f1da630d13de0370e2f6361f961f1c8b384af1c, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <7f798168c54455559da0f7a377a23ab7019fec35, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e701345d886e831fb593a0870d69c8c5de6fc938, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <e8f972b1759d26bbefe4c524caae1ed7c8a593bd, >=668c9beb9020d5834ee9e43c208190a07d2b1928 <fe5a23c76fc48b711eb7d6f3462c994e34da36f9 | 1bef1944ef15a40797305bf916827b04df6307ca, 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669, 4f1da630d13de0370e2f6361f961f1c8b384af1c, 7f798168c54455559da0f7a377a23ab7019fec35, e701345d886e831fb593a0870d69c8c5de6fc938, e8f972b1759d26bbefe4c524caae1ed7c8a593bd, fe5a23c76fc48b711eb7d6f3462c994e34da36f9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket