Answer in brief
CVE-2026-90013 records a Unknown severity vulnerability in tracing: Take trace_array reference when opening options file. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=577b785f55168d5acb3d123ba41bfe8d7981e044 <d0f37d77b9b4b241e0b30ef2562f6353cbda3bec || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5 || >=577b785f55168d5acb3d123ba41bfe8d7981e044 <f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73 | d0f37d77b9b4b241e0b30ef2562f6353cbda3bec, 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5, f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73 |
| Linux/Linuxgeneric | 2.6.30 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.