CVE-2026-68146

ftrace: Add global mutex to serialize trace_parser access

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.32 ≤ v < 5.10.2662.6.32 ≤ v < 5.15.2172.6.32 ≤ v < 6.1.1832.6.32 ≤ v < 6.12.1012.6.32 ≤ v < 6.18.422.6.32 ≤ v < 6.6.1482.6.32 ≤ v < 7.1.62.6.32 ≤ v < 7.22.6.32689fd8b65d669b96d612ccc37d6fb87bf7ed6907
Vendor states this is fixed in 1474fe4453505b6be720b5bb94be1c927de3314a (fixed)
Vendor states this is fixed in 3d0dd138a06c782f8b755cd1b6f9909494514ce1 (fixed)
Vendor states this is fixed in 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a (fixed)
Vendor states this is fixed in 7720b63bcef3f54c7fe288774b720a227d54a306 (fixed)
Vendor states this is fixed in 90be137813e1a5bdfd671e40fe28004fb959d3e4 (fixed)
Vendor states this is fixed in a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f (fixed)
Vendor states this is fixed in db76744d588086695371ecdd982694395628ba48 (fixed)
Vendor states this is fixed in e807c9193d9493c7a0d039158ebb955050a76df1 (fixed)
Vendor states this is fixed in 2.6.32 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card