← Back to search

CVE-2026-90013

7.8 HIGH

Published 2026-09-16 · Updated 2026-09-16

AI risk analysis

Summary
This flaw allows a use-after-free condition in the Linux kernel's tracing subsystem, which could lead to a kernel crash if an options file is opened by one task while another task removes the associated trace_array instance.
Exploitability
Exploitation requires concurrent access to the trace_array by multiple tasks, making it moderately difficult. Precondition is that the trace_array instance must be removed while an options file is still in use.
Blast radius
If exploited, this could result in a kernel crash, potentially leading to a denial of service condition.
Detection
No reliable host or network indicator is derivable from the published description.
Prioritized remediation
Upgrade to the latest stable kernel version, e.g., 'Upgrade to 5.10.100 or later'.
kerneluse-after-freestability

Analysis generated locally by qwen2.5:7b-instruct (no data left the box). AI-assisted — verify against primary sources before acting.

NVD description

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.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Data: NVD (public domain). Analysis: local $0 model. Defensive use only.