{"id":"CVE-2026-97934","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory corruption from a \"STACKTRACE\" histogram key\n\n\"cpu\", \"CPU\", \"stacktrace\" and \"STACKTRACE\" are generic fields, defined\nwith an offset and a size of z…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory corruption from a \"STACKTRACE\" histogram key\n\n\"cpu\", \"CPU\", \"stacktrace\" and \"STACKTRACE\" are generic fields, defined\nwith an offset and a size of z…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 4b512860bdbdddcf41467ebd394f27cb8dfb528c < 9e026a91fe79966e2baabd4345c6e3a26975c729","Linux >= 4b512860bdbdddcf41467ebd394f27cb8dfb528c < c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a","Linux >= 4b512860bdbdddcf41467ebd394f27cb8dfb528c < 7f711e62355bb3123a2ca2f97a2facbfebc678c6","Linux 6.4"],"published":"2026-09-25","updated":"2026-09-25","sourceUpdated":"2026-09-25T11:17:20.733","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97934","references":[{"url":"https://git.kernel.org/stable/c/7f711e62355bb3123a2ca2f97a2facbfebc678c6","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/9e026a91fe79966e2baabd4345c6e3a26975c729","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-25T11:06:38.884Z","slug":"CVE-2026-97934","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory corruption from a \"STACKTRACE\" histogram key\n\n\"cpu\", \"CPU\", \"stacktrace\" and \"STACKTRACE\" are generic fields, defined\nwith an offset and a size of zero so that the filter code can match them\nby name. parse_field() maps them onto their common_* equivalents for\nbackward compatibility, but unlike the common_* names it hands the\nplaceholder back to the caller instead of NULL.\n\ncreate_hist_field() takes a non-NULL field as a promise that the record\ncarries a stacktrace and picks HIST_FIELD_FN_STACK, so the __data_loc\nword is read from offset 0, that is from common_type, and its low 16\nbits are followed as an offset into the record. What is found there\nbecomes the length of an unbounded memcpy. Pick an event whose id is\nsmall enough that the offset stays inside its own record and the length\nis a kernel text address:\n\n  # cd /sys/kernel/tracing\n  # echo 'hist:keys=STACKTRACE' > events/ftrace/print/trigger\n  # echo hello > trace_marker\n\n  Oops: general protection fault, probably for non-canonical address\n  RIP: 0010:rb_next+0x23/0x60\n   </IRQ>\n  RIP: 0010:memcpy+0xc/0x30\n   event_hist_trigger+0x2e7/0x12c0\n  Kernel panic - not syncing: Fatal exception in interrupt\n\nLeave the field NULL, which is what the comment above the branch says\nthe code does and what common_stacktrace already does. FILTER_CPU and\nFILTER_COMM are left alone, their create_hist_field() branches never\nlook at the field.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}