All vulnerabilities

Servers and applications

CVE-2026-97924

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

Severity
Unrated
Published
25 Sept 2026
Last changed
30 Oct 2026
Added to UpHeron
30 Oct 2026
Fixed in
6.1.191, 6.6.158, 6.12.111, 6.18.53, 7.2.7
Exploit chance
0.2% in the next 30 daysHigher than 10% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

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.

From the CVE Program.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 5.18 before 6.1.191
  • From 6.2 before 6.6.158
  • From 6.7 before 6.12.111
  • From 6.13 before 6.18.53
  • From 6.19 before 7.2.7

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-97924