CVE-2026-68290

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

rds: tcp: unregister sysctl before tearing down listen socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80fffed08dc1c10e971066941d2daa56253f1552
generic

rds: tcp: unregister sysctl before tearing down listen socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3aa13fe0c1bb7bc5312f878e61523e5d8cf3f85d
generic

rds: tcp: unregister sysctl before tearing down listen socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16df2d154ec82e2f7e7585b4fa154751ba37729a
generic

rds: tcp: unregister sysctl before tearing down listen socket - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/167e54c703ccd4fa028feb568b0d1002020cff86

Vendor Advisories for CVE-2026-68290(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 31× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:29 UTCEG score recompute
  2. 2026-08-21 03:29 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:17 UTCGHSA enrichment
  5. 2026-08-20 00:10 UTCEG score recompute
  6. 2026-08-20 00:10 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:56 UTCGHSA enrichment
  9. 2026-08-18 21:44 UTCEG score recompute
  10. 2026-08-18 21:44 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:32 UTCGHSA enrichment
  14. 2026-08-17 19:20 UTCEG score recompute
  15. 2026-08-17 19:20 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:37 UTCEG score recompute
  18. 2026-08-17 05:37 UTCGHSA enrichment
  19. 2026-08-17 05:07 UTCEG score recompute
  20. 2026-08-17 05:07 UTCGHSA enrichment
  21. 2026-08-16 17:46 UTCEG score recompute
  22. 2026-08-16 17:46 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 04:34 UTCEG score recompute
  25. 2026-08-16 04:34 UTCGHSA enrichment
Show 18 more
  1. 2026-08-15 15:22 UTCGHSA enrichment
  2. 2026-08-15 02:10 UTCEG score recompute
  3. 2026-08-15 02:10 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 12:58 UTCEG score recompute
  6. 2026-08-14 12:58 UTCGHSA enrichment
  7. 2026-08-13 23:46 UTCEG score recompute
  8. 2026-08-13 23:46 UTCGHSA enrichment
  9. 2026-08-13 22:44 UTCEG score recompute 7.80
  10. 2026-08-13 22:44 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 08:16 UTCEG score recompute
  14. 2026-08-13 08:16 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-10 13:24 UTCNVD update
  17. 2026-08-10 12:19 UTCEG score recompute
  18. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68290?
CVE-2026-68290 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: rds: tcp: unregister sysctl before tearing down listen socket rdstcpexit_net() frees the per-netns RDS TCP listen socket via rdstcpkill_sock() before unregistering the per-netns sysctl table. Since rdstcpskbuf_handler() derives the…
When was CVE-2026-68290 disclosed?
CVE-2026-68290 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68290 actively exploited?
CVE-2026-68290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68290?
CVE-2026-68290 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68290?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68290, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68290

Explore →

Is Your Infrastructure Affected by CVE-2026-68290?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.