CVE-2023-54171 Details
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().
A memory leak vulnerability has been identified in the Linux kernel's tracing component. When reading the 'trace_pipe' file, the 'iter->temp' variable is allocated but not properly freed before 'trace_pipe' is closed. This oversight leads to unreferenced objects, as reported by kmemleak, indicating a memory management issue. The vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed by modifying the 'tracing_release_pipe()' function to include a call that frees 'iter->temp', ensuring proper memory management. Users can apply the latest patches available in the Linux kernel stable tree to remediate this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1a1e793e021d75cd0accd8f329ec9456e5cd105e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/3f42d57a76e7e96585f08855554e002218cbca0c | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/954792db9f61b6c0b8a94b8831fed5f146014029 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/be970e22c53d5572b2795b79da9716ada937023b | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d5a821896360cc8b93a15bd888fabc858c038dc0 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 30, 2025 | New CVE Received | kernel.org |
Volerion