CVE-2026-97934: tracing: Fix memory corruption from a "STACKTRACE" histogram key

Received
AliasesUBUNTU-CVE-2026-97934DEBIAN-CVE-2026-97934
Published 25-09-2026Last modified 21-10-2026

Vulnerability summary

CVE-2026-97934 is a vulnerability in linux with no CVSS score yet. EPSS estimates a 0.21% chance of exploitation in the next 30 days, higher than 10.8% of scored vulnerabilities.

Priority
Insufficient evidence

No CVSS vector published; no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
Not scored
010
No CVSS score recorded
EPSS score
0.21%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 34 · Related 30

Timeline

  1. 25-09-2026
    PublishedVulnerability first disclosed.
  2. 21-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

Risk metrics not yet published.

EPSS trend

Probability

0.21%

Chance of exploitation in the next 30 days

Percentile

11%

Versus all other CVEs

30-day change

Increase +0.01 pp

From 0.20% on 21-10-2026

21-10-202620-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: not stated in public data.

Ubuntu142 products
  • linuxAll versions (No fix recorded) | < 6.8.0-149.149 | < 7.0.0-42.42
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1069.74 | < 7.0.0-1016.17
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linuxAll versions (No fix recorded) | < 6.12.113-1 | < 7.2.7-1
  • linux-6.12< 6.12.113-1~deb12u1
Linux1 product
  • linux≥ 4b512860bdbdddcf41467ebd394f27cb8dfb528c, < c94985e4fd77eb8634f44fb42e551563c68c55b3 | ≥ 4b512860bdbdddcf41467ebd394f27cb8dfb528c, < b6cc6ec5f032ea6fd5cce94fb83baab4d1c02e33 | ≥ 4b512860bdbdddcf41467ebd394f27cb8dfb528c, < 9e026a91fe79966e2baabd4345c6e3a26975c729 | ≥ 4b512860bdbdddcf41467ebd394f27cb8dfb528c, < c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a | ≥ 4b512860bdbdddcf41467ebd394f27cb8dfb528c, < 7f711e62355bb3123a2ca2f97a2facbfebc678c6 | 6.4

3 vendors · 145 products

References

23 links
Show all 23 references