CVE-2026-80585

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

mptcp: fastopen: only mark MPTFO subflows with SYN data

Passive TCP Fast Open accepts a valid-cookie SYN even when it carries

no data. In that case the child socket's receive queue is intentionally

left empty.

mptcpfastopensubflowsynacksetparams() set ismptfo before checking

for queued SYN data. That made data-less TFO SYNs hit a WARN and, if

the warning was non-fatal, left stale MPTFO state behind. The stale

flag could later trigger a state-confusion bug in

checkfullyestablished().

Only mark the subflow as MPTFO after confirming that an SKB was queued.

Return quietly when the receive queue is empty.

Note that mptcpsubflowcontext's is_mptfo field is now not just about

subflows where the TFO was present, but about MPTFO subflow that

consumed SYN data. Only having a valid cookie but not carrying data is

not really "doing TFO".