CVE-2026-68377

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/sched: act_tunnel_key: Defer dst_release to RCU callback

Fix a race-condition use-after-free in tunnel_key_release_params().

The function releases the metadata_dst of the old params synchronously via dst_release() while deferring the params struct free with kfree_rcu(). A concurrent tunnel_key_act() reader on the datapath may still hold the old params pointer (under rcu_read_lock_bh) and proceed to call dst_clone(¶ms->tcft_enc_metadata->dst) after the writer's dst_release has already pushed the dst's rcuref to RCUREF_DEAD.

[email protected] produced a poc which i (and Victor) verified that KASAN reports:

================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:112 BUG: KASAN: slab-use-after-free in atomic_sub_return_release include/linux/atomic/atomic-instrumented.h:326 BUG: KASAN: slab-use-after-free in __rcuref_put include/linux/rcuref.h:109 BUG: KASAN: slab-use-after-free in rcuref_put include/linux/rcuref.h:173 BUG: KASAN: slab-use-after-free in dst_release+0x5b/0x370 net/core/dst.c:168 Write of size 4 at addr ffff88806158de40 by task poc/9388

CPU: 0 UID: 0 PID: 9388 Comm: poc Tainted: G W 7.1.0-rc7 #7 PREEMPT(lazy) Tainted: [W]=WARN Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 print_report+0x139/0x4ad mm/kasan/report.c:482 kasan_report+0xe4/0x1d0 mm/kasan/report.c:595 check_region_inline mm/kasan/generic.c:186 kasan_check_range+0x125/0x200 mm/kasan/generic.c:200 instrument_atomic_read_write include/linux/instrumented.h:112 atomic_sub_return_release include/linux/atomic/atomic-instrumented.h:326 __rcuref_put include/linux/rcuref.h:109 rcuref_put include/linux/rcuref.h:173 dst_release+0x5b/0x370 net/core/dst.c:168 refdst_drop include/net/dst.h:272 skb_dst_drop include/net/dst.h:284 skb_release_head_state+0x293/0x400 net/core/skbuff.c:1163 skb_release_all net/core/skbuff.c:1187 [..] Allocated by task 9391: kasan_save_stack+0x30/0x50 mm/kasan/common.c:57 kasan_save_track+0x14/0x30 mm/kasan/common.c:78 poison_kmalloc_redzone mm/kasan/common.c:398 __kasan_kmalloc+0x9a/0xb0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 __do_kmalloc_node mm/slub.c:5296 __kmalloc_noprof+0x2f1/0x830 mm/slub.c:5308 kmalloc_noprof include/linux/slab.h:954 kzalloc_noprof include/linux/slab.h:1188 offload_action_alloc+0x2f/0x130 net/core/flow_offload.c:35 tcf_action_offload_add_ex+0x1ba/0x880 net/sched/act_api.c:258 tcf_action_offload_add net/sched/act_api.c:293 tcf_action_init+0x66e/0xa20 net/sched/act_api.c:1547 tcf_action_add+0xf6/0x5d0 net/sched/act_api.c:2101 [..] Freed by task 9391: kasan_save_stack+0x30/0x50 mm/kasan/common.c:57 kasan_save_track+0x14/0x30 mm/kasan/common.c:78 kasan_save_free_info+0x3b/0x70 mm/kasan/generic.c:584 poison_slab_object mm/kasan/common.c:253 __kasan_slab_free+0x6b/0x90 mm/kasan/common.c:285 kasan_slab_free include/linux/kasan.h:235 slab_free_hook mm/slub.c:2689 slab_free mm/slub.c:6251 kfree+0x21f/0x6b0 mm/slub.c:6566 tcf_action_offload_add_ex+0x4ad/0x880 net/sched/act_api.c:284 tcf_action_offload_add net/sched/act_api.c:293 tcf_action_init+0x66e/0xa20 net/sched/act_api.c:1547 tcf_action_add+0xf6/0x5d0 net/sched/act_api.c:2101

The buggy address belongs to the object at ffff88806158de00 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 64 bytes inside of freed 256-byte region [ffff88806158de00, ffff88806158df00)

The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff88806158d600 pfn:0x6158c head: order:1 mapcount:0 entire_map ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.1%
EPSS %ILE
2nd
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 (5)

Auto-updated Aug 14, 2026
Patch available.
Web page

net/sched: act_tunnel_key: Defer dst_release to RCU callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fed1b1ddab41a0e7a462ac690a0c8af6ff793624
Web page

net/sched: act_tunnel_key: Defer dst_release to RCU callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1f5c8a3955f8fda3f84ed883ac8daa1847e724c
Web page

net/sched: act_tunnel_key: Defer dst_release to RCU callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/531dbb5bb98e52ad26be7e90f9f8bec707c5bd0e
Web page

net/sched: act_tunnel_key: Defer dst_release to RCU callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2791a501da508b704a617b4dba29db54a65bc9f7
Web page

net/sched: act_tunnel_key: Defer dst_release to RCU callback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2200a00ff247f70f5dcdb4e6f14b0d48ddac5467

Vendor Advisories for CVE-2026-68377(6)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-19ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-19ubuntu
redhatkernel-0:6.12.0-211.66.1.el10_22026-10-15redhat
redhatkernel-0:5.14.0-687.58.1.el9_82026-10-14redhat
redhatkernel-rt-0:4.18.0-553.174.1.rt7.515.el8_102026-10-14redhat
redhatkernel-0:4.18.0-553.174.1.el8_102026-10-14redhat

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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

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 23× in last 7d / 101× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 297 refreshes 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 197 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-68377?
CVE-2026-68377 is a high-severity vulnerability; its CVE record was published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: acttunnelkey: Defer dst_release to RCU callback Fix a race-condition use-after-free in tunnelkeyrelease_params(). The function releases the metadata_dst of the old params synchronously via dst_release() while deferring…
When was the CVE record for CVE-2026-68377 published?
The CVE record for CVE-2026-68377 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-68377 actively exploited?
CVE-2026-68377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68377?
CVE-2026-68377 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68377?
A fix for CVE-2026-68377 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68377 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-68377

Explore →

Is Your Infrastructure Affected by CVE-2026-68377?

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

Book a Demo →Browse All CVEs