tracing: Take trace_array reference when opening options file
CVE-2026-90013 · published 16 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90013?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 577b785f55168d5acb3d123ba41bfe8d7981e044 to < 8cc9c5a8c559d655c32d2190486e89574c14ff52, 577b785f55168d5acb3d123ba41bfe8d7981e044 to < 97ceaffbd672449ad7ead5ae8788dce16374b0c1, 577b785f55168d5acb3d123ba41bfe8d7981e044 to < d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 577b785f55168d5acb3d123ba41bfe8d7981e044 to < 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5
- Linux Linux: 2.6.30
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/8cc9c5a8c559d655c32d2190486e89574c14ff52
- git.kernel.org/stable/c/97ceaffbd672449ad7ead5ae8788dce16374b0c1
- git.kernel.org/stable/c/d0f37d77b9b4b241e0b30ef2562f6353cbda3bec
- git.kernel.org/stable/c/64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5
- git.kernel.org/stable/c/f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON