Vulnerability · Published Dec 30, 2025 · Assigned by Linux
CVE-2023-54171tracing: Fix memory leak of iter->temp when reading trace_pipe
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54171 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54171 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux | 5.15.0-86.96 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1047.52 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1049.56 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1049.56.1 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1044.52 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1044.49 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1030.35 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1040.43 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1043.49 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1044.49 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-86.95 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1037.37 | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1018.18 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1005.5 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1045.51 | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1040.43 | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54171 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54171 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ff895103a84abc85a5f43ecabc7f67cf36e1348f – before 1a1e793e021d75cd0accd8f329ec9456e5cd105eff895103a84abc85a5f43ecabc7f67cf36e1348f – before 954792db9f61b6c0b8a94b8831fed5f146014029ff895103a84abc85a5f43ecabc7f67cf36e1348f – before be970e22c53d5572b2795b79da9716ada937023bff895103a84abc85a5f43ecabc7f67cf36e1348f – before 3f42d57a76e7e96585f08855554e002218cbca0cff895103a84abc85a5f43ecabc7f67cf36e1348f – before d5a821896360cc8b93a15bd888fabc858c038dc0 |
| Linux | Linux | 5.7 |
References
- 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