Linux kernel use-after-free in TCP congestion info getsockopt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0baf26b0fcd74bbfcef53c5d5e8bad2b99c8d0d2 · < 86814e5370068ec2bf0caa6e6d55c3e5bfc6c324| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)
do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.
BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0 Read of size 8 at addr ffff888013701258 by task exploit/149 do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564) tcp_getsockopt+0x91/0xf0 __sys_getsockopt+0xf7/0x170
Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.
From the CVE record · Linux
The Linux kernel's TCP_CC_INFO getsockopt path can use a freed congestion-control function pointer. This can happen when BPF struct_ops congestion-control data is freed concurrently with the call. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with BPF struct_ops congestion control should check their kernel versions; affected versions are not specified.