CVE-2026-97924 json
tracing/user_events: Don't destroy fields when event removal fails
published last mo. modified 12d ago also EUVD-2026-86778
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.7-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-97924
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-97924
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.9-1.1
opensuse advisories openSUSE-SU-2026:12074-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-104424
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/c8efcb80f0b4d253482f9117db29bb92b4197d52 commit
- git.kernel.org/stable/c/a3d9b8b7c8f3627976fe758c77ffd3da260824d7 commit
- git.kernel.org/stable/c/9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b commit
- git.kernel.org/stable/c/0892da2272ec565858aa1ec5458552d699de9142 commit
- git.kernel.org/stable/c/62d6544e86506bb0695c9594c713cba859666f2f commit
- git.kernel.org/stable/c/2deb753127d7b7035e893955c5e91875e767d1f8 commit
Is CVE-2026-97924 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97924 updated cvss 5.5
kernel: tracing/user_events: Don't destroy fields when event removal fails
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c8efcb80f0b4d253482f9117db29bb92b4197d52
- git.kernel.org /stable/c/a3d9b8b7c8f3627976fe758c77ffd3da260824d7
- git.kernel.org /stable/c/9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b
- git.kernel.org /stable/c/0892da2272ec565858aa1ec5458552d699de9142
- git.kernel.org /stable/c/62d6544e86506bb0695c9594c713cba859666f2f
- git.kernel.org /stable/c/2deb753127d7b7035e893955c5e91875e767d1f8
Sources
- CVE List CVE-2026-97924
- NVD CVE-2026-97924
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.