Linux vulnerability

What happened

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.

Affected versions

Linux: 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before bcfeac79af740735ace44008b4a11b8e5add20f5 (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 8e9b56051d24540cfbf39194618708c4a7633549 (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 634a9af8a26a84d8b0d7b3b643204b344b42d9fb (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 7d2038d4b80166f7bead8d07eba3b97405816c21 (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 68667ee4c7dadf7f63167234e2a1af09b3f7874e (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before 6140cfa721451fa6e18e134e709703c2bf34d0fb (git); 668c9beb9020d5834ee9e43c208190a07d2b1928 through before f14fe6395a8b3d961a61e138ad7b36ba3626dd4e (git); 4.16 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.