CyberRota Analysis
AI-GeneratedThe vulnerability in the Linux kernel affects the RDS TCP listen socket, where the sysctl table is unregistered after the socket is freed, leading to a potential use-after-free condition during concurrent sysctl writes. This flaw could allow an attacker to exploit the race condition, resulting in system instability or unauthorized access to sensitive data. Organizations using affected Linux distributions should prioritize patching this vulnerability to mitigate potential risks associated with their network services.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: rds: tcp: unregister sysctl before tearing down listen socket rds_tcp_exit_net() frees the per-netns RDS TCP listen socket via rds_tcp_kill_sock() before unregistering the per-netns sysctl table. Since rds_tcp_skbuf_handler() derives the netns from rtn->rds_tcp_listen_sock->sk, a concurrent sysctl write can race with netns teardown and dereference the freed socket/sk. KASAN reports the race as: BUG: KASAN: slab-use-after-free in rds_tcp_skbuf_handler+0x2aa/0x2e0 rds_tcp_skbuf_handler net/rds/tcp.c:721 proc_sys_call_handler fs/proc/proc_sysctl.c vfs_write fs/read_write.c __x64_sys_pwrite64 fs/read_write.c Fix this by unregistering the RDS TCP sysctl table before calling rds_tcp_kill_sock(). unregister_net_sysctl_table() prevents new sysctl handlers from starting and waits for in-flight handlers to finish, so the listen socket can then be released safely. The fix was tested against the linked reproducer.