Trace parser corruption via concurrent descriptor writes
Published Aug 10, 2026 · Updated Aug 10, 2026
A race condition in Linux kernel ftrace allows local users to corrupt parser input by concurrently writing through one shared trace descriptor. The write and release handlers access the trace_parser idx, cont, and buffer fields without serialization, allowing threads to corrupt shared parsing state. Reaching these handlers requires local access to writable ftrace control files, and the documented consequence is corrupted input or undefined behavior.
Summary
What happened
A race condition in Linux kernel ftrace allows local users to corrupt parser input by concurrently writing through one shared trace descriptor. The write and release handlers access the trace_parser idx, cont, and buffer fields without serialization, allowing threads to corrupt shared parsing state. Reaching these handlers requires local access to writable ftrace control files, and the documented consequence is corrupted input or undefined behavior.
The record
- CVE
- CVE-2026-68146
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.32
- Affected versionversion=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <3d0dd138a06c782f8b755cd1b6f9909494514ce1
- Affected versionversion=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <65bf73bee1a4f3722208ae46afc0fa5de76b9a0a
- Affected versionversion=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <7720b63bcef3f54c7fe288774b720a227d54a306
- Affected versionversion=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <90be137813e1a5bdfd671e40fe28004fb959d3e4
- Affected versionversion=689fd8b65d669b96d612ccc37d6fb87bf7ed6907 <e807c9193d9493c7a0d039158ebb955050a76df1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo