# CVE-2026-97932: tracing: Don't dereference trace_event_file in deferred trigger free

> A use-after-free in the Linux kernel tracing subsystem allows local attackers to cause denial of service or potentially escalate privileges.

- **Severity:** Not scored
- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-97932, GHSA-pm4h-64gj-cjhp, UBUNTU-CVE-2026-97932

## What is CVE-2026-97932?

CVE-2026-97932 is an use after free vulnerability in Linux, published on 25 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: Don't dereference trace_event_file in deferred trigger free

The enable_event trigger defers trace_event_put_ref() to the
trigger free kthread, but the trace_event_file can already be freed
when the instance is removed.

Keep the trace_event_call directly in enable_trigger_data so the
deferred free does not access the freed trace_event_file.

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


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

Apply the vendor's patch.

## Is CVE-2026-97932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97932 is an use after free vulnerability in Linux, published on 25 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-97932 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-97932/ (Markdown: https://insights.sbomify.com/CVE-2026-97932/index.md)
```

## Sources

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

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