CVE-2026-90014: tracing: Have show_event_filters/triggers files take trace array ref

CVE-2026-90014: tracing: Have show_event_filters/triggers files take trace array ref

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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

tracing: Have show_event_filters/triggers files take trace array ref

The newly added files show_event_filters and show_event_triggers that show
all filters or triggers that are set within the trace array do not take a
reference for the trace array it is showing. Without taking a reference,
the trace_array may be freed via "rmdir" while a task is reading one of
theses files. Those files iterate all the events within an instance
(trace_array) and nothing prevents that instance from being freed while
its data is being read. This causes a use-after-free crash.

Have the open of both those files take the trace_array reference via the
trace_array_get() that prevents the trace_array from being freed while the
files are opened.

The Linux kernel CVE team has assigned CVE-2026-90014 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 7.0 with commit 729757b96a662d87e334fe8b837707800d8fd551 and fixed in 7.2.5 with commit 2ee3f7d43f79efaca0cd84a6798653d9d75ce60b
	Issue introduced in 7.0 with commit 729757b96a662d87e334fe8b837707800d8fd551 and fixed in 7.3-rc2 with commit f4a771cc684c7354b6200147f7252c58d17408ff

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-90014
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.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/2ee3f7d43f79efaca0cd84a6798653d9d75ce60b
	https://git.kernel.org/stable/c/f4a771cc684c7354b6200147f7252c58d17408ff