netfilter: synproxy: Fix out of bounds when parsing TCP options
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 48b1de4c110a7afa4b85862f6c75af817db26fad · < 9cdf299ba4e153b5e56187648420de22c6216f02| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: synproxy: Fix out of bounds when parsing TCP options
The TCP option parser in synproxy (synproxy_parse_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.").
v2 changes:
Added an early return when length < 0 to avoid calling skb_header_pointer with negative length.
From the CVE record · Linux
The Linux kernel's netfilter synproxy TCP option parser can read one byte beyond an option's length. A network attacker can trigger the read with a TCP option whose length is 1 and whose opcode is neither end-of-options nor no-operation. Authentication and user-interaction requirements are not specified.
Engineers running Linux kernels with netfilter synproxy should check whether their kernel includes the fix; affected versions are not specified.