All reports
Medium

kernel: sctp: fix race between sctp_wait_for_connect and peeloff

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-63971

Probability of exploitation in the next 30 days: 0.13%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: fix race between sctp_wait_for_connect and peeloff sctp_wait_for_connect() drops and re-acquires the socket lock while waiting for the association to reach ESTABLISHED state. During this window, another thread can peeloff the association to a new socket via getsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc->base.sk. After re-acquiring the old socket lock, sctp_wait_for_connect() returns success without noticing the migration — the caller then accesses the association under the wrong lock in sctp_datamsg_from_user(). Add the same sk != asoc->base.sk check that sctp_wait_for_sndbuf() already has, returning an error if the association was migrated while we slept.

A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A race condition exists in the sctp_wait_for_connect() function, where a socket lock is temporarily released and re-acquired. During this brief period, another process can move the SCTP association to a different socket. This can cause subsequent operations to access memory incorrectly, potentially leading to system instability or denial of service.