From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-38539: tracing: Add down_write(trace_event_sem) when adding trace event
Date: Sat, 16 Aug 2025 13:14:10 +0200 [thread overview]
Message-ID: <2025081657-CVE-2025-38539-fdcd@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tracing: Add down_write(trace_event_sem) when adding trace event
When a module is loaded, it adds trace events defined by the module. It
may also need to modify the modules trace printk formats to replace enum
names with their values.
If two modules are loaded at the same time, the adding of the event to the
ftrace_events list can corrupt the walking of the list in the code that is
modifying the printk format strings and crash the kernel.
The addition of the event should take the trace_event_sem for write while
it adds the new event.
Also add a lockdep_assert_held() on that semaphore in
__trace_add_event_dirs() as it iterates the list.
The Linux kernel CVE team has assigned CVE-2025-38539 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.31 with commit 110bf2b764eb6026b868d84499263cb24b1bcc8d and fixed in 6.1.147 with commit 7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b
Issue introduced in 2.6.31 with commit 110bf2b764eb6026b868d84499263cb24b1bcc8d and fixed in 6.6.100 with commit 6bc94f20a4c304997288f9a45278c9d0c06987d3
Issue introduced in 2.6.31 with commit 110bf2b764eb6026b868d84499263cb24b1bcc8d and fixed in 6.12.40 with commit 33e20747b47ddc03569b6bc27a2d6894c1428182
Issue introduced in 2.6.31 with commit 110bf2b764eb6026b868d84499263cb24b1bcc8d and fixed in 6.15.8 with commit 70fecd519caad0c1741c3379d5348c9000a5b29d
Issue introduced in 2.6.31 with commit 110bf2b764eb6026b868d84499263cb24b1bcc8d and fixed in 6.16 with commit b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df
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-2025-38539
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/7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b
https://git.kernel.org/stable/c/6bc94f20a4c304997288f9a45278c9d0c06987d3
https://git.kernel.org/stable/c/33e20747b47ddc03569b6bc27a2d6894c1428182
https://git.kernel.org/stable/c/70fecd519caad0c1741c3379d5348c9000a5b29d
https://git.kernel.org/stable/c/b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df
reply other threads:[~2025-08-16 11:14 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=2025081657-CVE-2025-38539-fdcd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.