CVE-2026-68146: ftrace: Add global mutex to serialize trace_parser access
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 1474fe4453505b6be720b5bb94be1c927de3314a, 3d0dd138a06c782f8b755cd1b6f9909494514ce1, 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1474fe4453505b6be720b5bb94be1c927de3314a, 3d0dd138a06c782f8b755cd1b6f9909494514ce1, 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Aug 10, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.32affected
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01faffected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before db76744d588086695371ecdd982694395628ba48affected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before 1474fe4453505b6be720b5bb94be1c927de3314aaffected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before 3d0dd138a06c782f8b755cd1b6f9909494514ce1affected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before 90be137813e1a5bdfd671e40fe28004fb959d3e4affected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before 65bf73bee1a4f3722208ae46afc0fa5de76b9a0aaffected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before e807c9193d9493c7a0d039158ebb955050a76df1affected · git
- 689fd8b65d669b96d612ccc37d6fb87bf7ed6907 and later · before 7720b63bcef3f54c7fe288774b720a227d54a306affected · git
- before 2.6.32not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68144Aug 10, 2026 · phonet: pep: fix use-after-free in pep_get_sb()39Monitor
- ← EarlierCVE-2026-68145Aug 10, 2026 · iomap: fix out-of-bounds bitmap_set() with zero-length range31Monitor
- Later →CVE-2026-68148Aug 10, 2026 · fscrypt: Add missing superblock check in find_or_insert_direct_key()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1474fe4453505b6be720b5bb94be1c927de3314a | Vendor (CNA) |
| Linux Linux | 3d0dd138a06c782f8b755cd1b6f9909494514ce1 | Vendor (CNA) |
| Linux Linux | 65bf73bee1a4f3722208ae46afc0fa5de76b9a0a | Vendor (CNA) |
| Linux Linux | 7720b63bcef3f54c7fe288774b720a227d54a306 | Vendor (CNA) |
| Linux Linux | 90be137813e1a5bdfd671e40fe28004fb959d3e4 | Vendor (CNA) |
| Linux Linux | a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f | Vendor (CNA) |
| Linux Linux | db76744d588086695371ecdd982694395628ba48 | Vendor (CNA) |
| Linux Linux | e807c9193d9493c7a0d039158ebb955050a76df1 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3d0dd138a06c782f8b755cd1b6f9909494514ce1
- git.kernel.org/stable/c/65bf73bee1a4f3722208ae46afc0fa5de76b9a0a
- git.kernel.org/stable/c/7720b63bcef3f54c7fe288774b720a227d54a306
- git.kernel.org/stable/c/90be137813e1a5bdfd671e40fe28004fb959d3e4
- git.kernel.org/stable/c/a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f
- git.kernel.org/stable/c/db76744d588086695371ecdd982694395628ba48
- git.kernel.org/stable/c/e807c9193d9493c7a0d039158ebb955050a76df1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.