CVE-2026-68146

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: 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:

ftrace: Add global mutex to serialize trace_parser access

In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input.

The affected handler paths and their specific functions are:

  • Open paths: ftrace_regex_open(), ftrace_graph_open()
  • Write paths: ftrace_regex_write(), ftrace_graph_write()
  • Release paths: ftrace_regex_release(), ftrace_graph_release()

If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser's internal state, specifically the 'idx', 'cont', and 'buffer' fields, leading to corrupted input or undefined behavior.

Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-68146(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 15× in last 7d / 22× 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 22:56 UTCEPSS rescore
  2. 2026-08-19 17:26 UTCGHSA enrichment
  3. 2026-08-19 17:21 UTCNVD update
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:55 UTCGHSA enrichment
  6. 2026-08-19 16:43 UTCMITRE cvelistV5
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 05:40 UTCGHSA enrichment
  10. 2026-08-17 05:26 UTCNVD update
  11. 2026-08-17 05:11 UTCGHSA enrichment
  12. 2026-08-17 05:05 UTCMITRE cvelistV5
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 10:42 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 12:05 UTCEG score recompute
  18. 2026-08-13 12:05 UTCGHSA enrichment
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-10 13:24 UTCNVD update
  21. 2026-08-10 12:21 UTCEG score recompute
  22. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68146?
CVE-2026-68146 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ftrace: Add global mutex to serialize trace_parser access In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user…
When was CVE-2026-68146 disclosed?
CVE-2026-68146 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-68146 actively exploited?
CVE-2026-68146 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 92.1% of all scored CVEs.
How do I remediate CVE-2026-68146?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68146, 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-68146

Explore →

Is Your Infrastructure Affected by CVE-2026-68146?

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