mptcp: plug races between subflow fail and subflow creation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mptcp: plug races between subflow fail and subflow creation
We have races similar to the one addressed by the previous patch between subflow failing and additional subflow creation. They are just harder to trigger.
The solution is similar. Use a separate flag to track the condition 'socket state prevent any additional subflow creation' protected by the fallback lock.
The socket fallback makes such flag true, and also receiving or sending an MP_FAIL option.
The field 'allow_infinite_fallback' is now always touched under the relevant lock, we can drop the ONCE annotation on write.
From the CVE record · Linux
The Linux kernel has a race between MPTCP subflow failure and creation of additional subflows, including when a socket falls back or sends or receives an MP_FAIL option. The input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with MPTCP should check their exposure; affected versions are not specified.