CVE-2026-63971
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Linux Kernel < 5.10.259
- Linux Kernel < 5.15.210
- Linux Kernel < 6.1.176
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.93
- Linux Kernel < 6.18.35
- Linux Kernel < 7.0.12
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63971.md and follow it. Check whether this project is affected by CVE-2026-63971. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d
- https://git.kernel.org/stable/c/6140cfa721451fa6e18e134e709703c2bf34d0fb
- https://git.kernel.org/stable/c/634a9af8a26a84d8b0d7b3b643204b344b42d9fb
- https://git.kernel.org/stable/c/68667ee4c7dadf7f63167234e2a1af09b3f7874e
- https://git.kernel.org/stable/c/7d2038d4b80166f7bead8d07eba3b97405816c21
- https://git.kernel.org/stable/c/8e9b56051d24540cfbf39194618708c4a7633549
- https://git.kernel.org/stable/c/bcfeac79af740735ace44008b4a11b8e5add20f5
- https://git.kernel.org/stable/c/f14fe6395a8b3d961a61e138ad7b36ba3626dd4e
References
- https://git.kernel.org/stable/c/0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d
- https://git.kernel.org/stable/c/6140cfa721451fa6e18e134e709703c2bf34d0fb
- https://git.kernel.org/stable/c/634a9af8a26a84d8b0d7b3b643204b344b42d9fb
- https://git.kernel.org/stable/c/68667ee4c7dadf7f63167234e2a1af09b3f7874e
- https://git.kernel.org/stable/c/7d2038d4b80166f7bead8d07eba3b97405816c21
- https://git.kernel.org/stable/c/8e9b56051d24540cfbf39194618708c4a7633549
- https://git.kernel.org/stable/c/bcfeac79af740735ace44008b4a11b8e5add20f5
- https://git.kernel.org/stable/c/f14fe6395a8b3d961a61e138ad7b36ba3626dd4e