Skip to main content
VulnerabilityPublished Updated

CVE-2026-68146: Linux kernel · ftrace: Add global mutex to serialize trace_parser access

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e807c9193d9493c7a0d039158ebb955050a76df1 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:19 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e807c9193d9493c7a0d039158ebb955050a76df1, db76744d588086695371ecdd982694395628ba48, a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < e807c9193d9493c7a0d039158ebb955050a76df1
Fixed in
  • e807c9193d9493c7a0d039158ebb955050a76df1
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < db76744d588086695371ecdd982694395628ba48
Fixed in
  • db76744d588086695371ecdd982694395628ba48
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f
Fixed in
  • a29bc20ea5f0cb79c6287f2c6182c5eeb8e6c01f
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < 7720b63bcef3f54c7fe288774b720a227d54a306
Fixed in
  • 7720b63bcef3f54c7fe288774b720a227d54a306
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < 1474fe4453505b6be720b5bb94be1c927de3314a
Fixed in
  • 1474fe4453505b6be720b5bb94be1c927de3314a
LinuxLinuxAffected
  • ≥ 689fd8b65d669b96d612ccc37d6fb87bf7ed6907, < 90be137813e1a5bdfd671e40fe28004fb959d3e4
Fixed in
  • 90be137813e1a5bdfd671e40fe28004fb959d3e4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and has been applied in the Linux kernel source code as indicated by multiple fixed commit versions. Users should update to a Linux kernel version that includes these fixes to prevent concurrent access issues in ftrace. No additional mitigation steps are required beyond applying the official patch.

Description

A concurrency vulnerability in the Linux kernel's ftrace subsystem was fixed by adding a global mutex to serialize access to the trace_parser structure. The issue occurred when multiple threads shared a trace file descriptor and concurrently wrote to it, causing race conditions that corrupted the parser's internal state. This could lead to corrupted input or undefined behavior during trace parsing.

References

Community reviews

Loading reviews…