bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 399040847084a69f345e0a52fd62f04654e0fce3 · < 31a420a822ff92e2090bd5d65efe8e34e2d6d9b8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie
bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie accept a socket pointer 'sk' with argument type ARG_PTR_TO_BTF_ID_SOCK_COMMON. However, they access sk->sk_protocol without validating whether 'sk' represents a full socket.
Fix this issue by checking sk->sk_state != TCP_LISTEN before inspecting sk->sk_protocol in both bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie. Since mini-sockets are never in the TCP_LISTEN state, the condition short-circuits and prevents dereferencing fullsock-specific fields.
From the CVE record · Linux
The Linux kernel’s BPF TCP syncookie helpers access sk_protocol without first checking whether the socket is a full socket. Supplying a mini-socket can cause access to a full-socket-specific field; the input does not specify attacker access requirements, user interaction, or further impact.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.