CVE-2026-63867: Linux kernel · mptcp: close TOCTOU race while computing rcv_wnd
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.2 High · fixed in c4f4cf60797974873dbc8e100144682a6f2f861f : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in c4f4cf60797974873dbc8e100144682a6f2f861f, 68364963e5baf03f16b4420292291f75c8f66497, 907ac6b1658e0277f979fcdfae2a753b495c1510 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: mptcp: close TOCTOU race while computing rcv_wnd The MPTCP output path access locklessly the MPTCP-level ack_seq in multiple times, using possibly different values for the data_ack in the DSS option and to compute the announced rcv wnd for the same packet. Refactor the cote to avoid inconsistencies which may confuse the peer. Also ensure that the MPTCP level rcv wnd is updated only when the egress packet actually contains a DSS ack.
References
- git.kernel.org/stable/c/301a33fd590c408a05c5df800e0cc1e6a8a2f8f8 (opens in a new tab)
- git.kernel.org/stable/c/68364963e5baf03f16b4420292291f75c8f66497 (opens in a new tab)
- git.kernel.org/stable/c/907ac6b1658e0277f979fcdfae2a753b495c1510 (opens in a new tab)
- git.kernel.org/stable/c/c4f4cf60797974873dbc8e100144682a6f2f861f (opens in a new tab)
- git.kernel.org/stable/c/3b8cbba7c0ed31189c89f90be247b8973ffa79ef (opens in a new tab)
- git.kernel.org/stable/c/8f4f0a157e8436a05bf8c3670b24dbc258911c43 (opens in a new tab)
- git.kernel.org/stable/c/8ab24fdebc369c0dfb90f82c1650b1e66662bb45 (opens in a new tab)