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.
Published: 2026-08-10
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

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.

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

Remediation

No vendor fix or workaround currently provided.

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
History

Sun, 23 Aug 2026 13:15:00 +0000


Wed, 19 Aug 2026 16:45:00 +0000


Wed, 12 Aug 2026 00:15:00 +0000

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


Mon, 10 Aug 2026 12:30:00 +0000

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

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-23T12:45:57.951Z

Reserved: 2026-07-30T09:28:09.371Z

Link: CVE-2026-68146

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T13:20:00.470

Modified: 2026-08-23T13:16:34.080

Link: CVE-2026-68146

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T11:59:11Z

Links: CVE-2026-68146 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T07:30:06Z

Weaknesses