rds: tcp: unregister sysctl before tearing down listen socket
CVE-2026-68290 · published 10 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-68290?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 to < 80fffed08dc1c10e971066941d2daa56253f1552, 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c to < 16df2d154ec82e2f7e7585b4fa154751ba37729a, 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c to < 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d, 7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c to < 167e54c703ccd4fa028feb568b0d1002020cff86
- Linux Linux: 6.13
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/80fffed08dc1c10e971066941d2daa56253f1552
- git.kernel.org/stable/c/16df2d154ec82e2f7e7585b4fa154751ba37729a
- git.kernel.org/stable/c/3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d
- git.kernel.org/stable/c/167e54c703ccd4fa028feb568b0d1002020cff86
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON