mptcp: allow subflow rcv wnd to shrink
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f3589be0c420a3137e5902d15705ced6a36f3f43 · < da23be77e1292cd611e736c3aa17da633d7ddce7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mptcp: allow subflow rcv wnd to shrink
In MPTCP connection, the `window` field in the TCP header refers to the MPTCP-level rcv_nxt and it's right edge should not move backward. Such constraint is enforced at DSS option generation time.
At the same time, the TCP stack ensures independently that the TCP-level rcv wnd right's edge does not move backward. That in turn causes artificial inflating of the MPTCP rcv window when the incoming data is acked at the TCP level and is OoO in the MPTCP sequence space (or lands in the backlog).
As a consequence, the incoming traffic can exceed the receiver rcvbuf size even when the sender is not misbehaving.
Prevent such scenario forcibly allowing the TCP subflow to shrink the TCP-level rcv wnd regardless of the current netns setting.
From the CVE record · Linux
The Linux kernel’s MPTCP receive window can become artificially inflated when incoming data is acknowledged at the TCP level but arrives out of order in MPTCP sequence space or lands in the backlog. Incoming network traffic can then exceed the receiver’s receive-buffer size even if the sender is not misbehaving. Authentication and user-interaction requirements are not specified.
Engineers running Linux kernels with MPTCP should check their kernel versions; affected versions are not specified.