tracing/user_events: Don't destroy fields when event removal fails
CVE-2026-97924 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-97924, released September 29, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| linux · Debian 13.5 (trixie) | 6.12.111-1 | DEBIAN-CVE-2026-97924 | Sep 29, 2026 |
| linux · Debian 14 | 7.2.7-1 | DEBIAN-CVE-2026-97924 | Sep 29, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-97924 | Sep 29, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.