CVE-2026-68117

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

Auto-updated Sep 30, 2026
Patch available.
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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.el8_102026-09-10redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 39× in last 7d / 257× 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.

Showing the most recent 100 of 498 total refreshes for this CVE.

  1. 2026-10-05 07:53 UTCEG score recompute
  2. 2026-10-05 07:53 UTCVendor advisory
  3. 2026-10-05 07:53 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 22:52 UTCVendor advisory
  6. 2026-10-04 22:52 UTCGHSA enrichment
  7. 2026-10-04 13:28 UTCVendor advisory
  8. 2026-10-04 13:28 UTCGHSA enrichment
  9. 2026-10-04 09:28 UTCVendor advisory
  10. 2026-10-04 09:28 UTCGHSA enrichment
  11. 2026-10-04 05:27 UTCEG score recompute
  12. 2026-10-04 05:27 UTCVendor advisory
  13. 2026-10-04 05:27 UTCGHSA enrichment
  14. 2026-10-03 14:26 UTCEPSS rescore
  15. 2026-10-03 00:56 UTCEG score recompute
  16. 2026-10-03 00:56 UTCVendor advisory
  17. 2026-10-03 00:56 UTCGHSA enrichment
  18. 2026-10-02 17:56 UTCEPSS rescore
  19. 2026-10-02 16:20 UTCVendor advisory
  20. 2026-10-02 16:20 UTCGHSA enrichment
  21. 2026-10-02 09:24 UTCEG score recompute
  22. 2026-10-02 09:24 UTCVendor advisory
  23. 2026-10-02 09:24 UTCGHSA enrichment
  24. 2026-10-01 19:50 UTCEPSS rescore
  25. 2026-10-01 14:55 UTCVendor advisory
Show 75 more
  1. 2026-10-01 14:55 UTCGHSA enrichment
  2. 2026-10-01 10:55 UTCVendor advisory
  3. 2026-10-01 10:55 UTCGHSA enrichment
  4. 2026-10-01 06:55 UTCVendor advisory
  5. 2026-10-01 06:55 UTCGHSA enrichment
  6. 2026-10-01 02:44 UTCVendor advisory
  7. 2026-10-01 02:44 UTCGHSA enrichment
  8. 2026-09-30 22:44 UTCEG score recompute
  9. 2026-09-30 22:44 UTCVendor advisory
  10. 2026-09-30 22:43 UTCGHSA enrichment
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 05:26 UTCEG score recompute
  13. 2026-09-29 05:26 UTCVendor advisory
  14. 2026-09-29 05:26 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 10:26 UTCVendor advisory
  17. 2026-09-28 10:26 UTCGHSA enrichment
  18. 2026-09-28 06:26 UTCVendor advisory
  19. 2026-09-28 06:26 UTCGHSA enrichment
  20. 2026-09-28 02:26 UTCVendor advisory
  21. 2026-09-28 02:26 UTCGHSA enrichment
  22. 2026-09-27 16:58 UTCEG score recompute
  23. 2026-09-27 16:58 UTCVendor advisory
  24. 2026-09-27 16:58 UTCGHSA enrichment
  25. 2026-09-27 13:48 UTCEPSS rescore
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-25 12:15 UTCVendor advisory
  28. 2026-09-25 12:15 UTCGHSA enrichment
  29. 2026-09-25 08:11 UTCVendor advisory
  30. 2026-09-25 08:11 UTCGHSA enrichment
  31. 2026-09-25 04:06 UTCEG score recompute
  32. 2026-09-25 04:06 UTCVendor advisory
  33. 2026-09-25 04:06 UTCGHSA enrichment
  34. 2026-09-24 13:35 UTCVendor advisory
  35. 2026-09-24 13:35 UTCGHSA enrichment
  36. 2026-09-24 09:34 UTCVendor advisory
  37. 2026-09-24 09:34 UTCGHSA enrichment
  38. 2026-09-24 05:28 UTCVendor advisory
  39. 2026-09-24 05:28 UTCGHSA enrichment
  40. 2026-09-24 01:14 UTCVendor advisory
  41. 2026-09-24 01:13 UTCGHSA enrichment
  42. 2026-09-23 21:13 UTCEG score recompute
  43. 2026-09-23 21:13 UTCVendor advisory
  44. 2026-09-23 21:13 UTCGHSA enrichment
  45. 2026-09-23 17:54 UTCEPSS rescore
  46. 2026-09-23 13:44 UTCVendor advisory
  47. 2026-09-23 13:44 UTCGHSA enrichment
  48. 2026-09-23 09:20 UTCVendor advisory
  49. 2026-09-23 09:20 UTCGHSA enrichment
  50. 2026-09-23 05:18 UTCVendor advisory
  51. 2026-09-23 05:18 UTCGHSA enrichment
  52. 2026-09-23 01:18 UTCVendor advisory
  53. 2026-09-23 01:18 UTCGHSA enrichment
  54. 2026-09-22 21:17 UTCEG score recompute
  55. 2026-09-22 21:17 UTCVendor advisory
  56. 2026-09-22 21:17 UTCGHSA enrichment
  57. 2026-09-22 15:23 UTCVendor advisory
  58. 2026-09-22 15:23 UTCGHSA enrichment
  59. 2026-09-22 11:18 UTCVendor advisory
  60. 2026-09-22 11:18 UTCGHSA enrichment
  61. 2026-09-22 07:18 UTCVendor advisory
  62. 2026-09-22 07:18 UTCGHSA enrichment
  63. 2026-09-22 03:17 UTCVendor advisory
  64. 2026-09-22 03:17 UTCGHSA enrichment
  65. 2026-09-21 23:16 UTCEG score recompute
  66. 2026-09-21 23:16 UTCVendor advisory
  67. 2026-09-21 23:16 UTCGHSA enrichment
  68. 2026-09-21 11:18 UTCVendor advisory
  69. 2026-09-21 11:17 UTCGHSA enrichment
  70. 2026-09-21 06:51 UTCVendor advisory
  71. 2026-09-21 06:51 UTCGHSA enrichment
  72. 2026-09-21 02:12 UTCVendor advisory
  73. 2026-09-21 02:11 UTCGHSA enrichment
  74. 2026-09-20 20:26 UTCEG score recompute
  75. 2026-09-20 20:26 UTCVendor advisory

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 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 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68117?
CVE-2026-68117 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68117?
A fix for CVE-2026-68117 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68117 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.