CVE-2026-63971sctp: fix race between sctp_wait_for_connect and peeloff
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (21 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < bcfeac79af740735ace44008b4a11b8e5add20f5
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 8e9b56051d24540cfbf39194618708c4a7633549
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 634a9af8a26a84d8b0d7b3b643204b344b42d9fb
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 7d2038d4b80166f7bead8d07eba3b97405816c21
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 68667ee4c7dadf7f63167234e2a1af09b3f7874e
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < 6140cfa721451fa6e18e134e709703c2bf34d0fb
- affected 668c9beb9020d5834ee9e43c208190a07d2b1928 – < f14fe6395a8b3d961a61e138ad7b36ba3626dd4e
- affected 4.16
- unaffected < 4.16
- unaffected 5.10.259 – ≤ 5.10.*
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.176 – ≤ 6.1.*
- unaffected 6.6.143 – ≤ 6.6.*
- unaffected 6.12.93 – ≤ 6.12.*
- unaffected 6.18.35 – ≤ 6.18.*
- unaffected 7.0.12 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d (opens in a new tab)
- https://git.kernel.org/stable/c/bcfeac79af740735ace44008b4a11b8e5add20f5 (opens in a new tab)
- https://git.kernel.org/stable/c/8e9b56051d24540cfbf39194618708c4a7633549 (opens in a new tab)
- https://git.kernel.org/stable/c/634a9af8a26a84d8b0d7b3b643204b344b42d9fb (opens in a new tab)
- https://git.kernel.org/stable/c/7d2038d4b80166f7bead8d07eba3b97405816c21 (opens in a new tab)
- https://git.kernel.org/stable/c/68667ee4c7dadf7f63167234e2a1af09b3f7874e (opens in a new tab)
- https://git.kernel.org/stable/c/6140cfa721451fa6e18e134e709703c2bf34d0fb (opens in a new tab)
- https://git.kernel.org/stable/c/f14fe6395a8b3d961a61e138ad7b36ba3626dd4e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45744 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-63971)Record last updated .