# CVE-2026-90014: tracing: Have show_event_filters/triggers files take trace array ref

> A use-after-free vulnerability in the Linux kernel tracing subsystem allows local attackers to cause a system crash by racing file reads with instance removal.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90014, GHSA-jcq3-vx22-85xp, UBUNTU-CVE-2026-90014

## What is CVE-2026-90014?

CVE-2026-90014 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

tracing: Have show_event_filters/triggers files take trace array ref

The newly added files show_event_filters and show_event_triggers that show
all filters or triggers that are set within the trace array do not take a
reference for the trace array it is showing. Without taking a reference,
the trace_array may be freed via "rmdir" while a task is reading one of
theses files. Those files iterate all the events within an instance
(trace_array) and nothing prevents that instance from being freed while
its data is being read. This causes a use-after-free crash.

Have the open of both those files take the trace_array reference via the
trace_array_get() that prevents the trace_array from being freed while the
files are opened.

## Which versions are affected by CVE-2026-90014?


## How do I fix CVE-2026-90014?

Apply the vendor's patch.

## Is CVE-2026-90014 being exploited?

There is no known exploitation of CVE-2026-90014 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90014 and fix it if it is affected.

What it is: CVE-2026-90014 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90014 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90014/ (Markdown: https://insights.sbomify.com/CVE-2026-90014/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90014
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90014
- OSV: https://osv.dev/vulnerability/CVE-2026-90014

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90014/
Summaries are generated and may contain mistakes; the official description above is the record.