CVE-2026-68146

published 10 Aug 2026 · updated 15 Nov 2026

ftrace: Add global mutex to serialize trace_parser access

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e807c9193d9493c7a0d039158ebb955050a76df1, Kernel 1474fe4453505b6be720b5bb94be1c927de3314a, Kernel 3d0dd138a06c782f8b755cd1b6f9909494514ce1 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <e807c9193d9493c7a0d039158ebb955050a76df1, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <1474fe4453505b6be720b5bb94be1c927de3314a, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <3d0dd138a06c782f8b755cd1b6f9909494514ce1, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <65bf73bee1a4f3722208ae46afc0fa5de76b9a0a, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <7720b63bcef3f54c7fe288774b720a227d54a306, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <90be137813e1a5bdfd671e40fe28004fb959d3e4, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f, >=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <db76744d588086695371ecdd982694395628ba48, =2.6.32e807c9193d9493c7a0d039158ebb955050a76df1, 1474fe4453505b6be720b5bb94be1c927de3314a, 3d0dd138a06c782f8b755cd1b6f9909494514ce1, 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a, 7720b63bcef3f54c7fe288774b720a227d54a306, 90be137813e1a5bdfd671e40fe28004fb959d3e4, a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f, db76744d588086695371ecdd982694395628ba48
linux-kernel: Kernel>=5.11.0 <5.15.217, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=2.6.32 <5.10.2665.15.217, 6.1.183, 6.18.42, 7.1.6, 6.6.148, 6.12.101, 5.10.266

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68146 severity on Zeptric[![CVE-2026-68146](https://zeptric.io/badge/cve/CVE-2026-68146.svg)](https://zeptric.io/cve/CVE-2026-68146)