CVE-2026-68146

ftrace: Add global mutex to serialize trace_parser access

Published Aug 10, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Linux kernel’s ftrace subsystem has a race condition in the trace_parser structure. When a trace file descriptor is shared across multiple threads, concurrent writes or releases can modify the parser’s internal fields, corrupting input or producing undefined behavior. This flaw can destabilize the kernel, potentially leading to system crashes or denial of service. The weakness is a classic race condition that compromises data integrity and reliability.

Affected Systems

All Linux kernel versions that include the vulnerable ftrace implementation and lack the guard added in the recent patch are affected. The vulnerability is mitigated by the introduction of a global mutex (parser_lock) that serializes access to trace_parser across open, write, and release operations. Specific workaround or product versions are not listed in the CNA data, so any kernel not patched for this change remains vulnerable.

Risk and Exploitability

The CVSS score is 5.3 and the EPSS score is less than 1%, indicating a medium severity vulnerability with a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, indicating it is not a known exploited flaw. The likely attack vector is a userspace process that opens a trace file descriptor and shares it among multiple threads, triggering concurrent parser access. While the flaw can cause catastrophic corruption, no direct privilege escalation or data exfiltration is described. The risk is considered moderate; the absence of known exploits and KEV listing reduces urgency, but the internal nature of the bug means any affected system could experience instability if left unpatched.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the parser_lock implementation for ftrace, ensuring all concurrent accesses are serialized.
  • If an immediate kernel upgrade is not feasible, restrict access to trace files to a single thread per descriptor or enforce synchronous write policies to avoid concurrent modifications as a temporary mitigation.
  • For custom kernel builds or environments that cannot adopt distribution patches immediately, apply the specific patch that adds parser_lock directly to the kernel source tree and rebuild the kernel.

Generated by OpenCVE AI on August 13, 2026 at 07:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4777-1 linux security update
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8961-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9029-1 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-820
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
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.
Title ftrace: Add global mutex to serialize trace_parser access
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 6, 2026, 4:44 PM
Reserved
Jul 30, 2026, 9:28 AM
Status
Received
Published
Aug 10, 2026, 1:20 PM
Modified
Nov 6, 2026, 5:19 PM
Severity
Moderate
Public date
Aug 10, 2026, 11:59 AM