mptcp: pm: fix ID 0 endp usage after multiple re-creations
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mptcp: pm: fix ID 0 endp usage after multiple re-creations
'local_addr_used' and 'add_addr_accepted' are decremented for addresses not related to the initial subflow (ID0), because the source and destination addresses of the initial subflows are known from the beginning: they don't count as "additional local address being used" or "ADD_ADDR being accepted".
It is then required not to increment them when the entrypoint used by the initial subflow is removed and re-added during a connection. Without this modification, this entrypoint cannot be removed and re-added more than once.
From the CVE record · Linux
The Linux kernel MPTCP path manager incorrectly counts an initial-subflow endpoint when it is removed and re-added during a connection. As a result, the endpoint cannot be removed and re-added more than once. The input does not specify an attacker action, access requirement, or user interaction.
Engineers running Linux kernels with MPTCP should check whether their kernel includes the fix; affected versions are not specified.