mptcp: do not account for OoO in mptcp_rcvbuf_grow()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.146.19.47.0In the Linux kernel, the following vulnerability has been resolved:
mptcp: do not account for OoO in mptcp_rcvbuf_grow()
MPTCP-level OoOs are physiological when multiple subflows are active concurrently and will not cause retransmissions nor are caused by drops.
Accounting for them in mptcp_rcvbuf_grow() causes the rcvbuf slowly drifting towards tcp_rmem[2].
Remove such accounting. Note that subflows will still account for TCP-level OoO when the MPTCP-level rcvbuf is propagated.
This also closes a subtle and very unlikely race condition with rcvspace init; active sockets with user-space holding the msk-level socket lock, could complete such initialization in the receive callback, after that the first OoO data reaches the rcvbuf and potentially triggering a divide by zero Oops.
From the CVE record · Linux
The Linux kernel’s MPTCP receive-buffer growth code accounts for out-of-order data across subflows, causing the receive buffer to drift upward. A rare race during receive-space initialization can also trigger a divide-by-zero Oops when an active socket’s lock is held by user space and the first out-of-order data reaches the receive buffer. The input does not specify an attacker access path or authentication requirements.
Engineers running Linux kernels with MPTCP should check their versions against the vendor advisory; affected versions are not specified.