net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4fbac77d2d092b475dda9eea66da674369665427 · < d6c686c01c5f12ff8f7264e0ddf71df6cb0d4414| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
When using a BPF program on kernel_connect(), the call can return -EPERM. This causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing the kernel to potentially freeze up.
Neil suggested:
This will propagate -EPERM up into other layers which might not be ready to handle it. It might be safer to map EPERM to an error we would be more likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.
ECONNREFUSED as error seems reasonable. For programs setting a different error can be out of reach (see handling in 4fbac77d2d09) in particular on kernels which do not have f10d05966196 ("bpf: Make BPF_PROG_RUN_ARRAY return -err instead of allow boolean"), thus given that it is better to simply remap for consistent behavior. UDP does handle EPERM in xs_udp_send_request().
From the CVE record · Linux
In the Linux kernel, SUNRPC TCP socket setup can loop indefinitely when a BPF program on kernel_connect() returns -EPERM. The loop fills the syslog and may freeze the kernel. The input does not establish whether an attacker can trigger this remotely or what access would be required.
Engineers running Linux kernels with BPF programs on kernel_connect() should check their kernel versions; affected versions are not specified in the input.