Dismissed
(max. allowed matches exceeded)
Permalink
CVE-2026-63971
7.8 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
sctp: fix race between sctp_wait_for_connect and peeloff
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.
References
Affected products
Linux
- <f14fe6395a8b3d961a61e138ad7b36ba3626dd4e
- <bcfeac79af740735ace44008b4a11b8e5add20f5
- =<6.18.*
- <8e9b56051d24540cfbf39194618708c4a7633549
- =<7.0.*
- <7d2038d4b80166f7bead8d07eba3b97405816c21
- <4.16
- =<5.15.*
- =<6.12.*
- <68667ee4c7dadf7f63167234e2a1af09b3f7874e
- <6140cfa721451fa6e18e134e709703c2bf34d0fb
- =<6.1.*
- =<6.6.*
- =<*
- <634a9af8a26a84d8b0d7b3b643204b344b42d9fb
- ==4.16
- <0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d
- =<5.10.*