CVE-2026-97934

tracing: Fix memory corruption from a "STACKTRACE" histogram key

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.

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.206% likely to be exploited in the next 30 days, higher than 10.748% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 4b512860bdbdddcf41467ebd394f27cb8dfb528c up to but excluding c94985e4fd77eb8634f44fb42e551563c68c55b3 (affected)
  • 4b512860bdbdddcf41467ebd394f27cb8dfb528c up to but excluding b6cc6ec5f032ea6fd5cce94fb83baab4d1c02e33 (affected)
  • 4b512860bdbdddcf41467ebd394f27cb8dfb528c up to but excluding 9e026a91fe79966e2baabd4345c6e3a26975c729 (affected)
  • 4b512860bdbdddcf41467ebd394f27cb8dfb528c up to but excluding c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a (affected)
  • 4b512860bdbdddcf41467ebd394f27cb8dfb528c up to but excluding 7f711e62355bb3123a2ca2f97a2facbfebc678c6 (affected)
LinuxLinux
  • Default status: affected
  • 6.4 (affected)
  • 0 up to but excluding 6.4 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References