mptcp: Fix out of bounds when parsing TCP options
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.10.465.12.135.13In the Linux kernel, the following vulnerability has been resolved:
mptcp: Fix out of bounds when parsing TCP options
The TCP option parser in mptcp (mptcp_get_options) could read one byte out of bounds. When the length is 1, the execution flow gets into the loop, reads one byte of the opcode, and if the opcode is neither TCPOPT_EOL nor TCPOPT_NOP, it reads one more byte, which exceeds the length of 1.
This fix is inspired by commit 9609dad263f8 ("ipv4: tcp_input: fix stack out of bounds when parsing TCP options.").
From the CVE record · Linux
The Linux kernel's MPTCP TCP option parser can read one byte out of bounds when a one-byte option has an opcode other than EOL or NOP. An attacker supplying such a TCP option could trigger the read; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with MPTCP should check their versions against the vendor advisory; affected versions are not specified.