CVE-2026-68146
CVE CVE-2026-68146EUVD EUVD-2026-55530Published 2026-08-10T11:59:11.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <90be137813e1a5bdfd671e40fe28004fb959d3e4; patch: 6.6.148; 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <3d0dd138a06c782f8b755cd1b6f9909494514ce1; patch: 7.2-rc5; patch: 6.12.101; patch: 7.1.6; 2.6.32; patch: 6.18.42; 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <e807c9193d9493c7a0d039158ebb955050a76df1; 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <65bf73bee1a4f3722208ae46afc0fa5de76b9a0a; 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <7720b63bcef3f54c7fe288774b720a227d54a306
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.