Answer in brief
CVE-2026-97932 records a Unknown severity vulnerability in tracing: Don't dereference trace_event_file in deferred trigger free. 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 | >=e091351b38818ef620d27f44f4bfd625f13afbff <67fb91a7f7bb1d958cf9cc249c912bca9b2fc821 || >=e091351b38818ef620d27f44f4bfd625f13afbff <bcfe2816e6ec46c3f4c58aa4264476665ddb3f69 || 159fdc3e01dca5fdbc412fcd8b239895733a270d || >=7.1.6 <7.2 | 67fb91a7f7bb1d958cf9cc249c912bca9b2fc821, bcfe2816e6ec46c3f4c58aa4264476665ddb3f69, 7.2 |
| Linux/Linuxgeneric | 7.2 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.