Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90013tracing: Take trace_array reference when opening options file

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90013, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < a6e15eadfdb6de30c24ef21b31f39a86359f4ab5
    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < 8cc9c5a8c559d655c32d2190486e89574c14ff52
    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < 97ceaffbd672449ad7ead5ae8788dce16374b0c1
    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < d0f37d77b9b4b241e0b30ef2562f6353cbda3bec
    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < 64a41f4a9a968f54f3792399aa4d2a9fdb23b0a5
    • affected 577b785f55168d5acb3d123ba41bfe8d7981e044 – < f2951ebd15c36a1ea4820a7f0cbb0b5f1c028b73
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90013 badge
[![CVE-2026-90013](https://cveledger.app/badge/CVE-2026-90013.svg)](https://cveledger.app/cve/CVE-2026-90013)

Record last updated .