mptcp: fix uninitialized local_id in syncookie MP_JOIN reconstruction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9466a1ccebbe54ac57fb8a89c2b4b854826546a8 · < 51887ccd88791ddaa8755a7c614fda031ecf7982| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mptcp: fix uninitialized local_id in syncookie MP_JOIN reconstruction
mptcp_token_join_cookie_init_state() restores remote_nonce, local_nonce, backup, join_id, token and msk from the saved cookie entry when rebuilding the request socket for a MP_JOIN 4th-ACK handled under SYN cookies, but it does not restore local_id, even though the SYN path saved it. subflow_ulp_clone() then reads that uninitialized field and stores it as the joined subflow's address-ID. Because the request-sock slab is SLAB_TYPESAFE_BY_RCU and not zeroed on allocation, the value is the stale byte of a previously freed request socket, which an off-path peer can influence by sending concurrent MP_JOIN SYNs. This corrupts the path manager's id-based subflow bookkeeping for the connection.
Restore subflow_req->local_id from the cookie entry, as done for the other fields.
From the CVE record · Linux
The Linux kernel fails to restore an address ID when reconstructing an MPTCP MP_JOIN request under SYN cookies. An off-path peer can influence the stale value by sending concurrent MP_JOIN SYNs, corrupting the connection's subflow bookkeeping.
Operators running Linux kernels with the affected MPTCP MP_JOIN code should check their kernel vendor's advisory; affected versions are not specified.