mptcp: fix sk_forward_memory corruption on retransmission
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 |
|
|
5.12.105.13In the Linux kernel, the following vulnerability has been resolved:
mptcp: fix sk_forward_memory corruption on retransmission
MPTCP sk_forward_memory handling is a bit special, as such field is protected by the msk socket spin_lock, instead of the plain socket lock.
Currently we have a code path updating such field without handling the relevant lock:
__mptcp_retrans() -> __mptcp_clean_una_wakeup()
Several helpers in __mptcp_clean_una_wakeup() will update sk_forward_alloc, possibly causing such field corruption, as reported by Matthieu.
Address the issue providing and using a new variant of blamed function which explicitly acquires the msk spin lock.
From the CVE record · Linux
The Linux kernel’s MPTCP retransmission path can update socket memory accounting without the required spin lock, potentially corrupting that accounting. The input does not specify how an attacker could trigger this path or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with MPTCP should check their versions; affected versions are not specified.