Answer in brief
CVE-2026-68290 records a Unknown severity vulnerability in rds: tcp: unregister sysctl before tearing down listen socket. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 <80fffed08dc1c10e971066941d2daa56253f1552 || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <16df2d154ec82e2f7e7585b4fa154751ba37729a || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <167e54c703ccd4fa028feb568b0d1002020cff86 || >=6.12.10 <6.12.101 | 80fffed08dc1c10e971066941d2daa56253f1552, 16df2d154ec82e2f7e7585b4fa154751ba37729a, 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d, 167e54c703ccd4fa028feb568b0d1002020cff86, 6.12.101 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68290 records a Unknown severity vulnerability in rds: tcp: unregister sysctl before tearing down listen socket. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=de8d6de0ee27be4b2b1e5b06f04aeacbabbba492 <80fffed08dc1c10e971066941d2daa56253f1552 || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <16df2d154ec82e2f7e7585b4fa154751ba37729a || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d || >=7f5611cbc4871c7fb1ad36c2e5a9edad63dca95c <167e54c703ccd4fa028feb568b0d1002020cff86 || >=6.12.10 <6.12.101 | 80fffed08dc1c10e971066941d2daa56253f1552, 16df2d154ec82e2f7e7585b4fa154751ba37729a, 3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d, 167e54c703ccd4fa028feb568b0d1002020cff86, 6.12.101 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.