CVE-2026-97934: Linux kernel · tracing: Fix memory corruption from a "STACKTRACE" histogram key
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c94985e4fd77eb8634f44fb42e551563c68c55b3 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c94985e4fd77eb8634f44fb42e551563c68c55b3, c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a, b6cc6ec5f032ea6fd5cce94fb83baab4d1c02e33 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory corruption from a "STACKTRACE" histogram key "cpu", "CPU", "stacktrace" and "STACKTRACE" are generic fields, defined with an offset and a size of zero so that the filter code can match them by name. parse_field() maps them onto their common_* equivalents for backward compatibility, but unlike the common_* names it hands the placeholder back to the caller instead of NULL. create_hist_field() takes a non-NULL field as a promise that the record carries a stacktrace and picks HIST_FIELD_FN_STACK, so the __data_loc word is read from offset 0, that is from common_type, and its low 16 bits are followed as an offset into the record. What is found there becomes the length of an unbounded memcpy. Pick an event whose id is small enough that the offset stays inside its own record and the length is a kernel text address: # cd /sys/kernel/tracing # echo 'hist:keys=STACKTRACE' > events/ftrace/print/trigger # echo hello > trace_marker Oops: general protection fault, probably for non-canonical address RIP: 0010:rb_next+0x23/0x60 </IRQ> RIP: 0010:memcpy+0xc/0x30 event_hist_trigger+0x2e7/0x12c0 Kernel panic - not syncing: Fatal exception in interrupt Leave the field NULL, which is what the comment above the branch says the code does and what common_stacktrace already does. FILTER_CPU and FILTER_COMM are left alone, their create_hist_field() branches never look at the field.
References
- git.kernel.org/stable/c/c94985e4fd77eb8634f44fb42e551563c68c55b3 (opens in a new tab)
- git.kernel.org/stable/c/b6cc6ec5f032ea6fd5cce94fb83baab4d1c02e33 (opens in a new tab)
- git.kernel.org/stable/c/9e026a91fe79966e2baabd4345c6e3a26975c729 (opens in a new tab)
- git.kernel.org/stable/c/c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a (opens in a new tab)
- git.kernel.org/stable/c/7f711e62355bb3123a2ca2f97a2facbfebc678c6 (opens in a new tab)