CVE-2026-97935: Linux kernel · tracing: Set the trace clock before registering the histogram trigger
Source GCVE Database
Not known to be exploited · fixed in cfad128171f8e2237a3c723d6478ef2cfb3b9127 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 17:19 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in cfad128171f8e2237a3c723d6478ef2cfb3b9127, cc6c4cf565b0c187c61ffd2e67a4dfb2427675ad, c7b77c22adcf314ec8aa4807f01914dcbc62ed54 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented in the Linux kernel to set the trace clock before registering the histogram trigger, preventing the use-after-free condition. Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.
Description
A use-after-free vulnerability in the Linux kernel tracing subsystem was fixed by setting the trace clock before registering the histogram trigger. The flaw allowed a named trigger to become findable before its clock was validated, leading to a use-after-free when an invalid clock was specified. This could cause a kernel crash due to accessing freed memory.
References
- nvd.nist.gov/vuln/detail/CVE-2026-97935 (opens in a new tab)
- git.kernel.org/stable/c/3568dabef3fb56517777ab981584f72ab1e90186 (opens in a new tab)
- git.kernel.org/stable/c/578d39ab420b18b76a12fc8d0573ec041a84da28 (opens in a new tab)
- git.kernel.org/stable/c/65d1e28198f344832a8a63e8ccf84b8f65b92a32 (opens in a new tab)
- git.kernel.org/stable/c/6ede78d0563a2a3ae3e46f9c07cedb5d79645429 (opens in a new tab)
- git.kernel.org/stable/c/85e6df6e9cd489de8e238596a68b89eee0c03b88 (opens in a new tab)
- git.kernel.org/stable/c/c7b77c22adcf314ec8aa4807f01914dcbc62ed54 (opens in a new tab)
- git.kernel.org/stable/c/cc6c4cf565b0c187c61ffd2e67a4dfb2427675ad (opens in a new tab)
- git.kernel.org/stable/c/cfad128171f8e2237a3c723d6478ef2cfb3b9127 (opens in a new tab)