VulnerabilityPublished 25 Sep 2026Updated 30 Oct 2026

CVE-2026-97924: Linux kernel · tracing/user_events: Don't destroy fields when event removal fails

Source GCVE Database

Compare

Authoritative record:CVE-2026-97924· Low

Not known to be exploited · fixed in c8efcb80f0b4d253482f9117db29bb92b4197d52 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 17:19 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in c8efcb80f0b4d253482f9117db29bb92b4197d52, a3d9b8b7c8f3627976fe758c77ffd3da260824d7, 0892da2272ec565858aa1ec5458552d699de9142 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-jx2m-2c39-9c87

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < c8efcb80f0b4d253482f9117db29bb92b4197d52	Fixed in c8efcb80f0b4d253482f9117db29bb92b4197d52
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < a3d9b8b7c8f3627976fe758c77ffd3da260824d7	Fixed in a3d9b8b7c8f3627976fe758c77ffd3da260824d7
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < 0892da2272ec565858aa1ec5458552d699de9142	Fixed in 0892da2272ec565858aa1ec5458552d699de9142
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < 62d6544e86506bb0695c9594c713cba859666f2f	Fixed in 62d6544e86506bb0695c9594c713cba859666f2f
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < 9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b	Fixed in 9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b
LinuxLinux	Affected ≥ 7f5a08c79df35e68f1a43033450c5050f12bc155, < 2deb753127d7b7035e893955c5e91875e767d1f8	Fixed in 2deb753127d7b7035e893955c5e91875e767d1f8

AI-suggested

A fix has been implemented that reorders the destruction of event fields to occur only after successful removal of the trace event call. Users should update their Linux kernel to a version that includes this fix once available. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel tracing subsystem could leave user event fields destroyed while the event remains registered if event removal fails. This inconsistent state occurs when the removal function returns a busy error, causing subsequent interactions to operate on an empty field list despite the event being visible in tracefs. The issue has been fixed by reordering the destruction of fields to occur only after successful event removal and restoring the field list if removal fails.

Impact

If event removal fails, the event remains registered with an empty field list, causing subsequent interactions to operate on incomplete data. This inconsistency could lead to incorrect tracing behavior or kernel instability related to user events in the tracing subsystem. There is no indication of remote code execution or privilege escalation from the provided data.

Summary

CVE-2026-97924 addresses a flaw in the Linux kernel's tracing/user_events component where destroy_user_event() prematurely destroys the event's fields before removing the trace event call. If user_event_set_call_visible() fails, for example due to the event still being enabled and trace_remove_event_call() returning -EBUSY, the event remains registered but with its fields irreversibly destroyed. This leads to inconsistent state and potential malfunction when interacting with the event. The fix moves field destruction after the call removal and restores the field list if removal fails, maintaining event consistency.

References

Community reviews

Loading reviews…