CVE-2026-97924

Unknown

Last modified

CVE-2026-97924 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7f5a08c79df35e68f1a43033450c5050f12bc155, < 9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b; >= 7f5a08c79df35e68f1a43033450c5050f12bc155, < 0892da2272ec565858aa1ec5458552d699de9142; >= 7f5a08c79df35e68f1a43033450c5050f12bc155, < 62d6544e86506bb0695c9594c713cba859666f2f; >= 7f5a08c79df35e68f1a43033450c5050f12bc155, < 2deb753127d7b7035e893955c5e91875e767d1f8
LinuxLinux5.18

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97924?
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.
How severe is CVE-2026-97924?
Severity scoring for CVE-2026-97924 is pending analysis.
How do I fix CVE-2026-97924?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-97924?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST