Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97935tracing: Set the trace clock before registering the histogram trigger

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 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 92.7% 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: Set the trace clock before registering the histogram trigger hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock: if (data->cmd_ops->init) { ret = data->cmd_ops->init(data); if (ret < 0) goto out; } if (hist_data->enable_timestamps) { ret = tracing_set_clock(file->tr, hist_data->attrs->clock); if (ret) { hist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); goto out; } The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object: ~# cd /sys/kernel/tracing/events/sched/sched_switch ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger bash: echo: write error: Invalid argument ~# echo 'hist:name=foo:keys=common_pid' > trigger BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0 Read of size 8 at addr ffff88800915d760 by task init/1 find_named_trigger+0xac/0xc0 hist_register_trigger+0xc1/0x900 event_hist_trigger_parse+0x3146/0x6af0 event_trigger_write+0xce/0x160 Freed by task 63: kfree+0x154/0x420 trigger_kthread_fn+0xfd/0x160 Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 ("tracing: Fix bad hist from corrupting named_triggers list") moved the registration below the rest of the setup. tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux a4072fe85ba3671720cab0788291af953db27318 – before 85e6df6e9cd489de8e238596a68b89eee0c03b88a4072fe85ba3671720cab0788291af953db27318 – before 3568dabef3fb56517777ab981584f72ab1e90186a4072fe85ba3671720cab0788291af953db27318 – before c7b77c22adcf314ec8aa4807f01914dcbc62ed54a4072fe85ba3671720cab0788291af953db27318 – before 578d39ab420b18b76a12fc8d0573ec041a84da28a4072fe85ba3671720cab0788291af953db27318 – before cc6c4cf565b0c187c61ffd2e67a4dfb2427675ada4072fe85ba3671720cab0788291af953db27318 – before cfad128171f8e2237a3c723d6478ef2cfb3b9127a4072fe85ba3671720cab0788291af953db27318 – before 65d1e28198f344832a8a63e8ccf84b8f65b92a32a4072fe85ba3671720cab0788291af953db27318 – before 6ede78d0563a2a3ae3e46f9c07cedb5d79645429
Linux Linux 4.17

References