From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99234: tracing: Unregister field variable histograms when the command fails
Date: Mon, 2 Nov 2026 17:04:17 +0100 [thread overview]
Message-ID: <2026110206-CVE-2026-99234-e15b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tracing: Unregister field variable histograms when the command fails
An action that names a field on another event needs that field as a
variable, so create_field_var_hist() registers a second hist trigger on
that event to provide it, and records it in
target_hist_data->field_var_hists[].
If a later part of the same command fails, create_actions() returns an
error and event_hist_trigger_parse() jumps to out_free. The write fails
with -EINVAL and sched_switch gets no trigger, but:
# echo 'hist:keys=pid:ts0=common_timestamp.usecs' >> \
events/sched/sched_waking/trigger
# echo 'my_synth u64 lat; int a; int b' >> synthetic_events
# echo 'hist:keys=next_pid:wakeup_lat=common_timestamp.usecs-$ts0:\
onmatch(sched.sched_waking).my_synth($wakeup_lat,prio,nosuchfld)'\
>> events/sched/sched_switch/trigger
# cat events/sched/sched_waking/trigger
hist:keys=pid:vals=hitcount:ts0=common_timestamp.usecs:sort=hitcount:size=2048:clock=global [active]
hist:keys=pid:vals=hitcount:synthetic_prio=prio:sort=hitcount:size=2048 [active]
The second histogram is the one created for 'prio'. It is still active and
still counting.
out_free reaches destroy_field_var_hists(), which frees the
field_var_hists[] entries, but never unregister_field_var_hists(), which is
what removes the triggers and runs only from event_hist_trigger_free(). The
entry is freed and the trigger is left with nothing tracking it.
Unregister the field variable histograms in out_free as well, and record
each one as soon as its trigger is registered rather than after the lookup
that follows it, so no exit can leave a registered trigger untracked. The
entry then belongs to field_var_hists[] and is released by
destroy_field_var_hists(), so freeing it on that exit would be a double
free.
The Linux kernel CVE team has assigned CVE-2026-99234 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 5.10.273 with commit f21351d1c4cdcc6a68f03636a407c2af1a5e1e10
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 5.15.224 with commit dba0f492703956801149cc70b39d2650a37995c3
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 6.1.191 with commit a3d7ffd2409700748a495b645948fef48199206e
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 6.6.161 with commit aae0ccd7326eef78dcdefffef3d1253e6f0615ca
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 6.12.115 with commit 8482ec5b65f606d5bbcec518e0afc69ad65ca414
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 6.18.60 with commit 431959fc76456cbba539279fe8967aa9391e6f23
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 7.2.14 with commit 5afb9317e2eeb1c7021a82995ce244fda5a4bd4f
Issue introduced in 4.17 with commit 02205a6752f223779a1b0e9e8ffacbea6e717851 and fixed in 7.3.1 with commit d0090baf02dd08f6e909f36f0ad54a4e80f5e79b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99234
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
kernel/trace/trace_events_hist.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f21351d1c4cdcc6a68f03636a407c2af1a5e1e10
https://git.kernel.org/stable/c/dba0f492703956801149cc70b39d2650a37995c3
https://git.kernel.org/stable/c/a3d7ffd2409700748a495b645948fef48199206e
https://git.kernel.org/stable/c/aae0ccd7326eef78dcdefffef3d1253e6f0615ca
https://git.kernel.org/stable/c/8482ec5b65f606d5bbcec518e0afc69ad65ca414
https://git.kernel.org/stable/c/431959fc76456cbba539279fe8967aa9391e6f23
https://git.kernel.org/stable/c/5afb9317e2eeb1c7021a82995ce244fda5a4bd4f
https://git.kernel.org/stable/c/d0090baf02dd08f6e909f36f0ad54a4e80f5e79b
https://git.kernel.org/stable/c/91c14d6c13096091c56304120aaa26e479130b8b
reply other threads:[~2026-11-02 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026110206-CVE-2026-99234-e15b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox