tracing/user_events: Don't destroy fields when event removal fails (CVE-2026-97924) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97924

tracing/user_events: Don't destroy fields when event removal fails

Answer in brief

CVE-2026-97924 records a Unknown severity vulnerability in tracing/user_events: Don't destroy fields when event removal fails. 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.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=7f5a08c79df35e68f1a43033450c5050f12bc155 <9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b \|\| >=7f5a08c79df35e68f1a43033450c5050f12bc155 <0892da2272ec565858aa1ec5458552d699de9142 \|\| >=7f5a08c79df35e68f1a43033450c5050f12bc155 <62d6544e86506bb0695c9594c713cba859666f2f \|\| >=7f5a08c79df35e68f1a43033450c5050f12bc155 <2deb753127d7b7035e893955c5e91875e767d1f8	9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b, 0892da2272ec565858aa1ec5458552d699de9142, 62d6544e86506bb0695c9594c713cba859666f2f, 2deb753127d7b7035e893955c5e91875e767d1f8
Linux/Linuxgeneric	5.18	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and trace_remove_event_call() returns -EBUSY, the event is left registered with an irreversibly destroyed field list. Any subsequent interaction with the event then operates on an empty field list while it is still fully visible in tracefs. Move the field destruction after the call removal, and splice the field list back onto the event when the removal fails so the event remains in a consistent state.

Quoted source text, attributed separately from HOL analysis.