CVE-2026-68117

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-55498 (ENISA EUVD) · GHSA-qmxc-qv48-vp67 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 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
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Nov 15, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1067.70) @ noble2026-11-18ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-11-18ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-18ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-18ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-18ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-11-18ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-18ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1025.26) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1070.70) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2022.23) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-11-18ubuntu
redhatkernel-0:6.12.0-211.67.1.el10_22026-10-19redhat
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
linuxKernel @ 5.10.265 (fixes >=0)—osv

These rows come from Ubuntu, Red Hat and OSV. 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 (162 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 18× in last 7d / 86× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 685 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 585 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 02:40 UTCEchelonGraph re-scored
  2. 2026-11-22 02:40 UTCVendor advisory
  3. 2026-11-22 02:40 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-21 01:01 UTCEchelonGraph re-scored
  6. 2026-11-21 01:01 UTCVendor advisory
  7. 2026-11-21 01:01 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-19 23:23 UTCEchelonGraph re-scored
  10. 2026-11-19 23:23 UTCVendor advisory
  11. 2026-11-19 23:23 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-18 20:55 UTCEchelonGraph re-scored
  14. 2026-11-18 20:55 UTCVendor advisory
  15. 2026-11-18 20:55 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  17. 2026-11-17 19:17 UTCEchelonGraph re-scored
  18. 2026-11-17 19:17 UTCVendor advisory
  19. 2026-11-17 19:16 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  21. 2026-11-16 17:35 UTCEchelonGraph re-scored
  22. 2026-11-16 17:35 UTCVendor advisory
  23. 2026-11-16 17:35 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  25. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.5% · 45th percentile
Show 75 more
  1. 2026-11-15 15:57 UTCEchelonGraph re-scored
  2. 2026-11-15 15:57 UTCVendor advisory
  3. 2026-11-15 15:56 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-14 14:18 UTCEchelonGraph re-scored
  6. 2026-11-14 14:18 UTCVendor advisory
  7. 2026-11-14 14:17 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-13 12:39 UTCEchelonGraph re-scored
  10. 2026-11-13 12:39 UTCVendor advisory
  11. 2026-11-13 12:39 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-12 11:01 UTCEchelonGraph re-scored
  14. 2026-11-12 11:01 UTCVendor advisory
  15. 2026-11-12 11:01 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-11 09:22 UTCEchelonGraph re-scored
  18. 2026-11-11 09:22 UTCVendor advisory
  19. 2026-11-11 09:22 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-11-10 07:43 UTCEchelonGraph re-scored
  22. 2026-11-10 07:43 UTCVendor advisory
  23. 2026-11-10 07:43 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-11-09 06:05 UTCEchelonGraph re-scored
  26. 2026-11-09 06:05 UTCVendor advisory
  27. 2026-11-09 06:05 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  29. 2026-11-08 04:26 UTCEchelonGraph re-scored
  30. 2026-11-08 04:26 UTCVendor advisory
  31. 2026-11-08 04:26 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  33. 2026-11-07 02:44 UTCEchelonGraph re-scored
  34. 2026-11-07 02:44 UTCVendor advisory
  35. 2026-11-07 02:44 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  37. 2026-11-06 15:55 UTCOSV refresh
  38. 2026-11-06 01:06 UTCEchelonGraph re-scored
  39. 2026-11-06 01:06 UTCVendor advisory
  40. 2026-11-06 01:06 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  42. 2026-11-04 23:26 UTCEchelonGraph re-scored
  43. 2026-11-04 23:26 UTCVendor advisory
  44. 2026-11-04 23:26 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  46. 2026-11-03 21:48 UTCEchelonGraph re-scored
  47. 2026-11-03 21:48 UTCVendor advisory
  48. 2026-11-03 21:48 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  50. 2026-11-02 20:09 UTCEchelonGraph re-scored
  51. 2026-11-02 20:09 UTCVendor advisory
  52. 2026-11-02 20:09 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  54. 2026-11-01 18:28 UTCEchelonGraph re-scored
  55. 2026-11-01 18:28 UTCVendor advisory
  56. 2026-11-01 18:28 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  58. 2026-10-31 16:49 UTCEchelonGraph re-scored
  59. 2026-10-31 16:49 UTCVendor advisory
  60. 2026-10-31 16:49 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  62. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  63. 2026-10-30 14:49 UTCEchelonGraph re-scored
  64. 2026-10-30 14:49 UTCVendor advisory
  65. 2026-10-30 14:49 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  67. 2026-10-29 13:11 UTCEchelonGraph re-scored
  68. 2026-10-29 13:11 UTCVendor advisory
  69. 2026-10-29 13:10 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  71. 2026-10-28 11:29 UTCEchelonGraph re-scored
  72. 2026-10-28 11:29 UTCVendor advisory
  73. 2026-10-28 11:29 UTCGHSA enrichmentGHSA-qmxc-qv48-vp67 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  75. 2026-10-27 09:23 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-68117?
CVE-2026-68117 is a critical-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-68117 published?
The CVE record for CVE-2026-68117 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
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 (45th 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.