CVE-2026-90013

published 16 Sep 2026 · updated 7 Nov 2026

tracing: Take trace_array reference when opening options file

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, Kernel 8cc9c5a8c559d655c32d2190486e89574c14ff52, Kernel 97ceaffbd672449ad7ead5ae8788dce16374b0c1 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: tracing: Take trace_array reference when opening options file The options files do not take the trace_array reference for the options they represent. This could cause a use-after-free kernel crash if one of these files is opened by one task and another task removes the instance that the option is for. Because it doesn't take a reference upon opening, it will not stop the removal which will free the options descriptor that is being used. As the options are somewhat dynamic in their creation at boot up, each file represents a flag in the trace_array. The trace_array has an array of indexes to represent each of these flags that is stored in the trace_flags_index array. The address of the index array element is used to pass to the inode->i_private pointer. Then that element is read which holds the index (which represents the flag) and then the index is used to calculate the trace_array descriptor from its trace_flags_index array. One issue is that the index element can not be referenced until the trace_array's reference is taken. To handle this, create a new helper function called: trace_array_options_get() that will iterate all the existing trace_arrays in the ftrace_trace_arrays list (under the trace_types_lock), and compare the passed in address of the index element with the entire array of the trace_array's trace_flags_index array. If it matches, then up the corresponding trace_array's reference and return.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.30, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <8cc9c5a8c559d655c32d2190486e89574c14ff52, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <97ceaffbd672449ad7ead5ae8788dce16374b0c1, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <a6e15eadfdb6de30c24ef21b31f39a86359f4ab5, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b7364a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, 8cc9c5a8c559d655c32d2190486e89574c14ff52, 97ceaffbd672449ad7ead5ae8788dce16374b0c1, a6e15eadfdb6de30c24ef21b31f39a86359f4ab5, d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90013 severity on Zeptric[![CVE-2026-90013](https://zeptric.io/badge/cve/CVE-2026-90013.svg)](https://zeptric.io/cve/CVE-2026-90013)