Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97933tracing: Take trace_array reference when opening a tracer options file

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

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 89.3% 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: Take trace_array reference when opening a tracer options file When a tracer option file is opened, it is passed a descriptor that points to an element on the trace_array's topts array. This element has information to find the trace array and other information. It uses this element to take a reference of the trace_array so that the trace_array does not get removed while this file is opened. Unfortunately, there's a race condition where the element itself could be freed by the removal of the instance the trace_array represents causing a use-after-free as this element that is used to find the trace_array to increment its reference counter is also freed when the instance is removed. To solve this, add a trace_array_tracer_options_get() helper function that will take the address of the element that is passed to the open function by the inode->i_private pointer and search all the trace_arrays under a lock to find the one that the element's address is in the range of the trace_arrays topts array elements. When a match happens, that trace_array's reference would be increased. Note, there's a race where if an admin was deleting and creating trace instances at the same time and the memory of the old trace_array's array matched the memory of the new trace_array that it could in theory open the option from the wrong trace array. But we do not care because it would be stupid to perform that kind of action. As long as the only thing that can happen is that the option from the wrong trace array is used and doesn't crash the kernel it will only make the user confused. But if they are doing something stupid like this, they are already confused, so no harm done.

Affected packages & fixed versions

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

Affected products (as reported)

VendorProductVersions
Linux Linux 7e2cfbd2d3c86afcd5c26b5c4b1dd251f63c5838 – before 61894ea0d2a1ae8ce903abf73bd56958c035f1827e2cfbd2d3c86afcd5c26b5c4b1dd251f63c5838 – before b2890064a12efbeb3b3c093e69e9010dd244c8817e2cfbd2d3c86afcd5c26b5c4b1dd251f63c5838 – before d9232a90c6f7de822177d35d73d9234cba523ef97e2cfbd2d3c86afcd5c26b5c4b1dd251f63c5838 – before b2fb87d29ffb3a7a9ccc5acf12898ecb805874277e2cfbd2d3c86afcd5c26b5c4b1dd251f63c5838 – before ed0aff60f83a9bdc2f6556376ac79c96b3ce7e80952e477f908048145a5eb2ed3d431d9efc1e1073b3183f5f05cd867f5c17122773ca5aa8d07b51afbf38c1d29f8bfe9631b62a67f8dd1b8f7efb7139
Linux Linux 6.6

References