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-90002

ftrace: Take trace_array reference before accessing its ftrace_ops

Description

In the Linux kernel, the following vulnerability has been resolved: ftrace: Take trace_array reference before accessing its ftrace_ops The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel. Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used. This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.

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-90002, 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.17% · top 94% of all CVEs (11 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 591dffdade9f07692a7dd3ed16830ec24e901ece – < 0124b36a7eac1dd0402146fc6c1f732877b9cd9f
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < ffe16fe221e25cd1915602e6753c3d3285ed9a98
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < 8f062a6bfeb4b4e18d469a673aec23a7b73c3e8a
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < 29266da8ee1d9be656b1f22460c49538e1930658
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < 177cd8966325f0ffffa3c9381f9e0422019a3973
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < 83fd7eca5ab0d3ac3f23bff889175d847e21af06
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < cee8f286794df916553d8d445eac5c323ec5b0f8
    • affected 591dffdade9f07692a7dd3ed16830ec24e901ece – < 9100191e5acb2e5ea2313f436667bb5fce129f47
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .