Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97936tracing: Fix memory corruption from the histogram stacktrace modifier

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory corruption from the histogram stacktrace modifier parse_field() sets HIST_FIELD_FL_STACKTRACE from the ".stacktrace" modifier before it looks the field name up, and nothing afterwards checks that the name resolved to a field which holds a stacktrace. create_hist_field() picks HIST_FIELD_FN_STACK on the strength of the field pointer alone, which reads a __data_loc word from the record and follows its low 16 bits as an offset into the same record. event_hist_trigger() takes the first word there as an entry count and copies that many longs into a 31 entry array: n_entries = *stack; memcpy(entries, ++stack, n_entries * sizeof(unsigned long)); Neither end of that copy is bounded, and the count is whatever the event holds at the offset, so any field will do: # cd /sys/kernel/tracing/events/sched/sched_process_fork # echo 'hist:keys=parent_pid.stacktrace' > trigger # (true) BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:rb_insert_color+0x18/0x130 timerqueue_linked_add+0x7e/0xd0 enqueue_hrtimer+0x39/0xb0 __hrtimer_run_queues+0x10f/0x1f0 </IRQ> RIP: 0010:memcpy+0xc/0x30 event_hist_trigger+0x165/0x690 The timer interrupt landed on the rbtree the copy had already run over. No debug options are needed for this; KASAN reports the same write as an out-of-bounds read of 13835058055416381440 bytes. Documentation/trace/histogram.rst already states the rule, "must be a long[] type", so enforce it once the name has been resolved. Names which resolve to no field at all, "hitcount.stacktrace" and the common_* pseudo-fields, are refused for the same reason: they hold no stacktrace to read.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.111-1DEBIAN-CVE-2026-97936
Debian:14linux7.2.7-1DEBIAN-CVE-2026-97936
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-97936
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97936
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-97936
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-97936
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-97936

Affected products (as reported)

VendorProductVersions
Linux Linux cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314 – before 98da3379cdee343f671dac89b9afbd8b071f2591cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314 – before e183b84968d4a6ea476d806ea97668405aa56880cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314 – before 57bfc2a17954d173d2a4182f3b582ffbb23aff64cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314 – before 55caaf25da2c2bb9b75307e4c868726cb954b1d6cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314 – before a5e70ba87ca8ebc79b4e63de302d03b0625fe153
Linux Linux 6.3

References