CVE-2026-99233 json
tracing/histograms: Verify event_call identity when updating synth_event refcount
published 2026-11-02 6 d ago modified 2026-11-03 5 d ago also EUVD-2026-115275
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
tracing/histograms: Verify event_call identity when updating synth_event refcount
In event_hist_trigger_parse() and hist_unreg_all(), the histogram registration and unregistration paths look up find_synth_event() using trace_event_name(file->event_call) and adjust se->ref if a match is found.
Because find_synth_event() only compares the event basename, registering or removing a histogram on a non-synthetic trace event whose basename matches a synthetic event erroneously modifies the synthetic event's reference count. If a histogram is registered on the non-synthetic event before the synthetic event is created and removed afterwards, se->ref is decremented without a matching increment, allowing the synthetic event to be freed while an active histogram action still holds a pointer to it.
Introduce find_synth_event_call() to verify that &se->call matches file->event_call before adjusting se->ref.
Patch / fix
- Linux Linux 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1, 7.4-rc1
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.14-1
debian advisories DEBIAN-CVE-2026-99233
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112565
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/381f543ed35c434d5b707369aa5dcd69ecf440af commit
- git.kernel.org/stable/c/4472579bd1c83708b6fe623c870cdf728e947205 commit
- git.kernel.org/stable/c/23b4106e8b35823acc79e206c7745f55b9cfd78b commit
- git.kernel.org/stable/c/06e816bed499fe47f39f12044382cc5d064485fb commit
- git.kernel.org/stable/c/5597bb8db6855fcb97a67196d227fea359bcd81c commit
- git.kernel.org/stable/c/cf4e31d5da80fae4c9cdbe7af55b7c3ad213f0e4 commit
- git.kernel.org/stable/c/3403d9bb27ebc3572bd048620746b4414e073bf9 commit
Vendor 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-99233 updated cvss 7.8
kernel: kernel: Privilege escalation via use-after-free in tracing subsystem
-
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-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9, openshift/ose-rhel-coreos-10affected: workaround, no fix available
-
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 morenot affected: vulnerable code not present
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.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/381f543ed35c434d5b707369aa5dcd69ecf440af
- git.kernel.org /stable/c/4472579bd1c83708b6fe623c870cdf728e947205
- git.kernel.org /stable/c/23b4106e8b35823acc79e206c7745f55b9cfd78b
- git.kernel.org /stable/c/06e816bed499fe47f39f12044382cc5d064485fb
- git.kernel.org /stable/c/5597bb8db6855fcb97a67196d227fea359bcd81c
- git.kernel.org /stable/c/cf4e31d5da80fae4c9cdbe7af55b7c3ad213f0e4
- git.kernel.org /stable/c/3403d9bb27ebc3572bd048620746b4414e073bf9
Sources
- CVE List CVE-2026-99233
- NVD CVE-2026-99233
Fencer Vulns 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.