[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123021-CVE-2023-54171-5524@gregkh>
Date: Tue, 30 Dec 2025 13:09:39 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54171: tracing: Fix memory leak of iter->temp when reading trace_pipe
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix memory leak of iter->temp when reading trace_pipe
kmemleak reports:
unreferenced object 0xffff88814d14e200 (size 256):
comm "cat", pid 336, jiffies 4294871818 (age 779.490s)
hex dump (first 32 bytes):
04 00 01 03 00 00 00 00 08 00 00 00 00 00 00 00 ................
0c d8 c8 9b ff ff ff ff 04 5a ca 9b ff ff ff ff .........Z......
backtrace:
[<ffffffff9bdff18f>] __kmalloc+0x4f/0x140
[<ffffffff9bc9238b>] trace_find_next_entry+0xbb/0x1d0
[<ffffffff9bc9caef>] trace_print_lat_context+0xaf/0x4e0
[<ffffffff9bc94490>] print_trace_line+0x3e0/0x950
[<ffffffff9bc95499>] tracing_read_pipe+0x2d9/0x5a0
[<ffffffff9bf03a43>] vfs_read+0x143/0x520
[<ffffffff9bf04c2d>] ksys_read+0xbd/0x160
[<ffffffff9d0f0edf>] do_syscall_64+0x3f/0x90
[<ffffffff9d2000aa>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
when reading file 'trace_pipe', 'iter->temp' is allocated or relocated
in trace_find_next_entry() but not freed before 'trace_pipe' is closed.
To fix it, free 'iter->temp' in tracing_release_pipe().
The Linux kernel CVE team has assigned CVE-2023-54171 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit ff895103a84abc85a5f43ecabc7f67cf36e1348f and fixed in 5.10.188 with commit 1a1e793e021d75cd0accd8f329ec9456e5cd105e
Issue introduced in 5.7 with commit ff895103a84abc85a5f43ecabc7f67cf36e1348f and fixed in 5.15.121 with commit 954792db9f61b6c0b8a94b8831fed5f146014029
Issue introduced in 5.7 with commit ff895103a84abc85a5f43ecabc7f67cf36e1348f and fixed in 6.1.40 with commit be970e22c53d5572b2795b79da9716ada937023b
Issue introduced in 5.7 with commit ff895103a84abc85a5f43ecabc7f67cf36e1348f and fixed in 6.4.5 with commit 3f42d57a76e7e96585f08855554e002218cbca0c
Issue introduced in 5.7 with commit ff895103a84abc85a5f43ecabc7f67cf36e1348f and fixed in 6.5 with commit d5a821896360cc8b93a15bd888fabc858c038dc0
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-2023-54171
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.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/1a1e793e021d75cd0accd8f329ec9456e5cd105e
https://git.kernel.org/stable/c/954792db9f61b6c0b8a94b8831fed5f146014029
https://git.kernel.org/stable/c/be970e22c53d5572b2795b79da9716ada937023b
https://git.kernel.org/stable/c/3f42d57a76e7e96585f08855554e002218cbca0c
https://git.kernel.org/stable/c/d5a821896360cc8b93a15bd888fabc858c038dc0
Powered by blists - more mailing lists