CVE-2026-99634: mptcp: do not use Fast Open on MP_JOIN subflows

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mptcp: do not use Fast Open on MPJOIN subflows

tcpfastopencreatechild() hands the SYN packet itself to subflowsynrecvsock(). For an MPJOIN request this takes the fatal fallback: the cloned child is destroyed and handed back with dropreq flagged, but tcpfastopencreatechild() does not check the flag and queues it, so accept() can expose the freed child.

MPJOIN cannot use Fast Open: data on a subflow requires the completed HMAC exchange (RFC 8684, sec. 3.2). Refuse it (only the TFO path passes a SYN skb here) and let tcpconnrequest() fall back to the regular MPJOIN handshake; also strip the Fast Open cookie from MPJOIN SYN/ACKs.

[ Moving code to avoid clearing TS and consolidating checks. ]

Affected Software

3 affected componentsFixes available
linux/kernel>=5.8.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    Do not use Fast Open on MP_JOIN subflows: refuse Fast Open for MP_JOIN requests and fall back to the regular MP_JOIN handshake; also strip the Fast Open cookie from MP_JOIN SYN/ACKs.

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel's Multipath TCP implementation are exposed when an MP_JOIN subflow is processed through the TCP Fast Open path. The issue concerns MP_JOIN requests rather than ordinary TCP Fast Open connections.

2

What would an attacker need to do to trigger the vulnerable path?

An attacker would need to send an MP_JOIN request that reaches the TCP Fast Open child-creation path. In that path, a freed cloned child can be queued and later exposed through accept().

3

Is TCP Fast Open valid for MP_JOIN subflows?

No. MP_JOIN subflows cannot use Fast Open because subflow data requires completion of the MP_JOIN HMAC exchange. The fix rejects Fast Open for MP_JOIN and falls back to the regular MP_JOIN handshake.

4

What mitigation is available if the fix cannot be applied immediately?

The provided data identifies the risky condition as use of the TCP Fast Open path for MP_JOIN requests. Avoiding that combination mitigates exposure; the fixed behavior also removes Fast Open cookies from MP_JOIN SYN/ACKs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203