Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68146ftrace: Add global mutex to serialize trace_parser access

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < db76744d588086695371ecdd982694395628ba48
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < 1474fe4453505b6be720b5bb94be1c927de3314a
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < 3d0dd138a06c782f8b755cd1b6f9909494514ce1
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < 90be137813e1a5bdfd671e40fe28004fb959d3e4
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < e807c9193d9493c7a0d039158ebb955050a76df1
    • affected 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 – < 7720b63bcef3f54c7fe288774b720a227d54a306
  • Linux · Linux

    • affected 2.6.32
    • unaffected < 2.6.32
    • unaffected 5.10.266 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68146 badge
[![CVE-2026-68146](https://cveledger.app/badge/CVE-2026-68146.svg)](https://cveledger.app/cve/CVE-2026-68146)

Record last updated .