CVE-2026-68177

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 — 4 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:

tracing: Delay module ref count for "enable_event" trigger

Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enable_event data is put into the private_data_free() callback, but the put of the module refcount is done immediately.

It is possible that if a module is removed that has an event that would enable (or disable) it is still active, it can read the data of the module after it is removed causing a use-after-free bug.

Move the trace_event_put_ref() that releases the module into the delayed callback so that the module can not be removed until any reference to its events are finished.

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
5%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

tracing: Delay module ref count for "enable_event" trigger - kernel/git/stable/linux.git - Linux kernel stable tree

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

tracing: Delay module ref count for "enable_event" trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/159fdc3e01dca5fdbc412fcd8b239895733a270d

Vendor Advisories for CVE-2026-68177(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 34× in last 7d / 40× 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-20 08:24 UTCGHSA enrichment
  2. 2026-08-19 20:12 UTCEG score recompute
  3. 2026-08-19 20:12 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 07:59 UTCGHSA enrichment
  6. 2026-08-18 19:47 UTCEG score recompute
  7. 2026-08-18 19:47 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 07:34 UTCGHSA enrichment
  10. 2026-08-17 19:20 UTCEG score recompute
  11. 2026-08-17 19:20 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 05:40 UTCEG score recompute
  14. 2026-08-17 05:40 UTCGHSA enrichment
  15. 2026-08-17 05:10 UTCEG score recompute
  16. 2026-08-17 05:10 UTCGHSA enrichment
  17. 2026-08-17 00:46 UTCEG score recompute
  18. 2026-08-17 00:46 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 12:33 UTCEG score recompute
  21. 2026-08-16 12:33 UTCGHSA enrichment
  22. 2026-08-16 00:21 UTCGHSA enrichment
  23. 2026-08-15 12:08 UTCEG score recompute
  24. 2026-08-15 12:08 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 15 more
  1. 2026-08-14 23:55 UTCGHSA enrichment
  2. 2026-08-14 11:42 UTCEG score recompute
  3. 2026-08-14 11:42 UTCGHSA enrichment
  4. 2026-08-13 23:30 UTCEG score recompute
  5. 2026-08-13 23:30 UTCGHSA enrichment
  6. 2026-08-13 22:45 UTCEG score recompute 7.80
  7. 2026-08-13 22:45 UTCGHSA enrichment
  8. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 09:49 UTCEG score recompute
  11. 2026-08-13 09:49 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-10 13:24 UTCNVD update
  14. 2026-08-10 12:20 UTCEG score recompute
  15. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68177?
CVE-2026-68177 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: tracing: Delay module ref count for "enable_event" trigger Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enable_event data is put into the…
When was CVE-2026-68177 disclosed?
CVE-2026-68177 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-68177 actively exploited?
CVE-2026-68177 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 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68177?
CVE-2026-68177 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68177, 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-68177

Explore →

Is Your Infrastructure Affected by CVE-2026-68177?

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