CVE-2026-97932: Linux kernel · tracing: Don't dereference trace_event_file in deferred trigger free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bcfe2816e6ec46c3f4c58aa4264476665ddb3f69 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in bcfe2816e6ec46c3f4c58aa4264476665ddb3f69, 67fb91a7f7bb1d958cf9cc249c912bca9b2fc821, 7.2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to bcfe2816e6ec46c3f4c58aa4264476665ddb3f69, 67fb91a7f7bb1d958cf9cc249c912bca9b2fc821 or 7.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in Linux kernel version 7.2 and specific commits identified by hashes bcfe2816e6ec46c3f4c58aa4264476665ddb3f69 and 67fb91a7f7bb1d958cf9cc249c912bca9b2fc821. Users and administrators should upgrade to version 7.2 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
A use-after-free vulnerability in the Linux kernel's tracing subsystem was fixed by preventing dereferencing of a freed trace_event_file during deferred trigger free operations. This issue occurred because the enable_event trigger deferred freeing a trace_event reference to a kernel thread, but the trace_event_file could already be freed when the instance was removed. The fix involved keeping the trace_event_call directly in enable_trigger_data to avoid accessing freed memory.