CVE-2026-68117

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.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:

tipc: clear sock->sk on the failed-insert path in tipc_sk_create()

When tipc_sk_create() fails to insert the new socket (tipc_sk_insert() returns non-zero), its error path frees the sk with sk_free() but leaves sock->sk pointing at the freed object:

if (tipc_sk_insert(tsk)) { sk_free(sk); pr_warn("Socket create failed; port number exhausted\n"); return -EINVAL; }

This is harmless for plain socket(): the syscall layer clears sock->ops before releasing, so tipc_release() is never called. It is not harmless on the accept() path. tipc_accept() creates the pre-allocated child socket with tipc_sk_create(net, new_sock, 0, kern); on failure it leaves new_sock->sk dangling and new_sock->ops non-NULL, and do_accept() then fput()s the new file, so __sock_release() -> tipc_release() runs lock_sock(new_sock->sk) on the freed sk -- a use-after-free write of the sk_lock spinlock.

tipc_release() already guards this exact "failed accept() releases a pre-allocated child" case with "if (sk == NULL) return 0;", but the guard is bypassed because tipc_sk_create() left sock->sk non-NULL (dangling) rather than NULL.

Clear sock->sk on the failed-insert path so the existing tipc_release() NULL check fires and the use-after-free is avoided.

The tipc_sk_insert() failure is reached when the per-netns socket rhashtable hits its max_size (tsk_rht_params.max_size = 1048576, ~2M elements) -- i.e. once a netns holds ~2M TIPC sockets every insert returns -E2BIG.

BUG: KASAN: slab-use-after-free in lock_sock_nested (net/core/sock.c:3839) Write of size 8 at addr ffff8880047cdc38 by task init/1 lock_sock_nested (net/core/sock.c:3839) tipc_release (net/tipc/socket.c:638) __sock_release (net/socket.c:710) sock_close (net/socket.c:1501) __fput (fs/file_table.c:512) Allocated by task 1: sk_alloc (net/core/sock.c:2308) tipc_sk_create (net/tipc/socket.c:487) tipc_accept (net/tipc/socket.c:2744) do_accept (net/socket.c:2034) Freed by task 1: __sk_destruct (net/core/sock.c:2391) tipc_sk_create (net/tipc/socket.c:504) tipc_accept (net/tipc/socket.c:2744) do_accept (net/socket.c:2034)

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

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

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9596b1566616a8be0592dbceccb6344a7c6f6bb
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/efebc23e9b29e3e5a9e2127dd066929f7f0d315e
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd29891ed840f6b8d020b759d0dc4a00b1d6e4ea
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba0533fc163f905fe817cfabdf8ed4058da44800
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b07d87b31631edb6529e6cdcca790a7489d1250d
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d6f26d48e61ef34f1921289401dbf36b10816af
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82f59aa27f33bd014a7d8739371ab5712d15e33b
generic

tipc: clear sock->sk on the failed-insert path in tipc_sk_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f5a41a48dbf9eda57b67ce23e548602cf7195a6

Vendor Advisories for CVE-2026-68117(2)

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 62× in last 7d / 77× 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 06:20 UTCVendor advisory
  2. 2026-08-21 06:20 UTCGHSA enrichment
  3. 2026-08-21 02:20 UTCEG score recompute
  4. 2026-08-21 02:20 UTCVendor advisory
  5. 2026-08-21 02:20 UTCGHSA enrichment
  6. 2026-08-20 22:56 UTCEPSS rescore
  7. 2026-08-20 22:19 UTCGHSA enrichment
  8. 2026-08-20 18:18 UTCGHSA enrichment
  9. 2026-08-20 14:17 UTCGHSA enrichment
  10. 2026-08-20 09:27 UTCGHSA enrichment
  11. 2026-08-20 05:27 UTCGHSA enrichment
  12. 2026-08-20 01:27 UTCGHSA enrichment
  13. 2026-08-19 21:27 UTCGHSA enrichment
  14. 2026-08-19 17:26 UTCEG score recompute
  15. 2026-08-19 17:26 UTCGHSA enrichment
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-19 16:55 UTCEG score recompute
  18. 2026-08-19 16:55 UTCGHSA enrichment
  19. 2026-08-19 15:42 UTCGHSA enrichment
  20. 2026-08-19 11:41 UTCGHSA enrichment
  21. 2026-08-19 07:41 UTCGHSA enrichment
  22. 2026-08-19 03:41 UTCGHSA enrichment
  23. 2026-08-18 23:40 UTCGHSA enrichment
  24. 2026-08-18 19:39 UTCGHSA enrichment
  25. 2026-08-18 15:38 UTCEG score recompute
Show 52 more
  1. 2026-08-18 15:38 UTCGHSA enrichment
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-18 11:30 UTCGHSA enrichment
  4. 2026-08-18 07:28 UTCGHSA enrichment
  5. 2026-08-18 03:28 UTCGHSA enrichment
  6. 2026-08-17 23:22 UTCGHSA enrichment
  7. 2026-08-17 19:22 UTCEG score recompute
  8. 2026-08-17 19:22 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 13:41 UTCGHSA enrichment
  11. 2026-08-17 09:41 UTCGHSA enrichment
  12. 2026-08-17 05:41 UTCEG score recompute
  13. 2026-08-17 05:41 UTCGHSA enrichment
  14. 2026-08-17 05:12 UTCEG score recompute
  15. 2026-08-17 05:12 UTCGHSA enrichment
  16. 2026-08-17 03:35 UTCGHSA enrichment
  17. 2026-08-16 23:35 UTCGHSA enrichment
  18. 2026-08-16 19:35 UTCGHSA enrichment
  19. 2026-08-16 15:34 UTCEG score recompute
  20. 2026-08-16 15:34 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 11:33 UTCGHSA enrichment
  23. 2026-08-16 07:33 UTCGHSA enrichment
  24. 2026-08-16 03:33 UTCEG score recompute
  25. 2026-08-16 03:33 UTCGHSA enrichment
  26. 2026-08-15 23:33 UTCGHSA enrichment
  27. 2026-08-15 19:33 UTCGHSA enrichment
  28. 2026-08-15 15:33 UTCGHSA enrichment
  29. 2026-08-15 11:33 UTCGHSA enrichment
  30. 2026-08-15 07:33 UTCGHSA enrichment
  31. 2026-08-15 03:32 UTCEG score recompute
  32. 2026-08-15 03:32 UTCGHSA enrichment
  33. 2026-08-15 01:30 UTCEPSS rescore
  34. 2026-08-14 23:31 UTCGHSA enrichment
  35. 2026-08-14 19:31 UTCGHSA enrichment
  36. 2026-08-14 15:31 UTCGHSA enrichment
  37. 2026-08-14 11:31 UTCGHSA enrichment
  38. 2026-08-14 07:31 UTCGHSA enrichment
  39. 2026-08-14 03:31 UTCEG score recompute
  40. 2026-08-14 03:31 UTCGHSA enrichment
  41. 2026-08-13 23:31 UTCEG score recompute
  42. 2026-08-13 23:31 UTCGHSA enrichment
  43. 2026-08-13 22:46 UTCEG score recompute 9.80
  44. 2026-08-13 22:46 UTCGHSA enrichment
  45. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  46. 2026-08-13 22:00 UTCEPSS rescore
  47. 2026-08-13 17:00 UTCEG score recompute
  48. 2026-08-13 17:00 UTCGHSA enrichment
  49. 2026-08-12 13:51 UTCEPSS rescore
  50. 2026-08-10 13:24 UTCNVD update
  51. 2026-08-10 12:22 UTCEG score recompute
  52. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68117?
CVE-2026-68117 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: tipc: clear sock->sk on the failed-insert path in tipcskcreate() When tipcskcreate() fails to insert the new socket (tipcskinsert() returns non-zero), its error path frees the sk with sk_free() but leaves sock->sk pointing at the…
When was CVE-2026-68117 disclosed?
CVE-2026-68117 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68117 actively exploited?
CVE-2026-68117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68117?
CVE-2026-68117 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68117?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68117, 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-68117

Explore →

Is Your Infrastructure Affected by CVE-2026-68117?

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