CVE-2026-63971
Analyzed
Analyzed - Analysis Complete
Race Condition in Linux Kernel SCTP Socket Handling
Vulnerability report for CVE-2026-63971, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-07-19
Last updated on: 2026-10-02
Assigner: kernel.org
Description
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.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.176 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.35 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.143 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.93 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.210 (exc) |
| linux | linux_kernel | 7.1 |
| linux | linux_kernel | From 6.19 (inc) to 7.0.12 (exc) |
| linux | linux_kernel | From 4.16 (inc) to 5.10.259 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |