mptcp: avoid deadlock on fallback while reinjecting
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
1d82a8fe6ee4afdc92f4e8808c9dad2a6095bbc5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mptcp: avoid deadlock on fallback while reinjecting
Jakub reported an MPTCP deadlock at fallback time:
WARNING: possible recursive locking detected 6.18.0-rc7-virtme #1 Not tainted -------------------------------------------- mptcp_connect/20858 is trying to acquire lock: ff1100001da18b60 (&msk->fallback_lock){+.-.}-{3:3}, at: __mptcp_try_fallback+0xd8/0x280
but task is already holding lock: ff1100001da18b60 (&msk->fallback_lock){+.-.}-{3:3}, at: __mptcp_retrans+0x352/0xaa0
other info that might help us debug this: Possible unsafe locking scenario:
CPU0 ---- lock(&msk->fallback_lock); lock(&msk->fallback_lock);
*** DEADLOCK ***
From the CVE record · Linux
The Linux kernel’s MPTCP fallback path can deadlock when the packet scheduler attempts reinjection after receiving an MP_FAIL but before the infinite map has been transmitted. This can occur during packet transmission; the input does not establish whether an attacker can trigger it or what access would be required.
Engineers running Linux kernels with MPTCP should check whether their kernel includes the fix; affected versions are not specified.