CVE-2026-68290

HighCVSS 7.8

Published: 10/08/2026(UTC)Updated: 17/08/2026(UTC)Translated: 10/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.13%

3th percentile - higher than 3% of all known CVEs

Summary

In the Linux kernel, the RDS TCP module has a race condition during netns teardown. The sysctl is unregistered after closing the listen socket, which can lead to use-after-free in rds_tcp_skbuf_handler().

Risk Assessment

A local attacker could exploit the race to cause a system crash or potentially execute code in the kernel. However, this requires write access to sysctl.

Recommendation

Apply the Linux kernel patch that unregisters the sysctl table before closing the listen socket. Reboot the system after the update.

Original NVD description (English source)

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.