Vulnerability · Published Jul 25, 2025 · Assigned by Linux
CVE-2025-38418remoteproc: core: Release rproc->clean_table after rproc_attach() fails
Medium 5.5
In plain English
A medium-severity 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 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: remoteproc: core: Release rproc->clean_table after rproc_attach() fails When rproc->state = RPROC_DETACHED is attached to remote processor through rproc_attach(), if rproc_handle_resources() returns failure, then the clean table should be released, otherwise the following memory leak will occur. unreferenced object 0xffff000086a99800 (size 1024): comm "kworker/u12:3", pid 59, jiffies 4294893670 (age 121.140s) hex dump (first 32 bytes): 00 00 00 00 00 80 00 00 00 00 00 00 00 00 10 00 ............ 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 ............ backtrace: [<000000008bbe4ca8>] slab_post_alloc_hook+0x98/0x3fc [<000000003b8a272b>] __kmem_cache_alloc_node+0x13c/0x230 [<000000007a507c51>] __kmalloc_node_track_caller+0x5c/0x260 [<0000000037818dae>] kmemdup+0x34/0x60 [<00000000610f7f57>] rproc_boot+0x35c/0x56c [<0000000065f8871a>] rproc_add+0x124/0x17c [<00000000497416ee>] imx_rproc_probe+0x4ec/0x5d4 [<000000003bcaa37d>] platform_probe+0x68/0xd8 [<00000000771577f9>] really_probe+0x110/0x27c [<00000000531fea59>] __driver_probe_device+0x78/0x12c [<0000000080036a04>] driver_probe_device+0x3c/0x118 [<000000007e0bddcb>] __device_attach_driver+0xb8/0xf8 [<000000000cf1fa33>] bus_for_each_drv+0x84/0xe4 [<000000001a53b53e>] __device_attach+0xfc/0x18c [<00000000d1a2a32c>] device_initial_probe+0x14/0x20 [<00000000d8f8b7ae>] bus_probe_device+0xb0/0xb4 unreferenced object 0xffff0000864c9690 (size 16):
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.147-1 | DEBIAN-CVE-2025-38418 |
| Debian:13 | linux | 6.12.35-1 | DEBIAN-CVE-2025-38418 |
| Debian:14 | linux | 6.12.35-1 | DEBIAN-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux | 5.15.0-156.166 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux | 6.8.0-100.100 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1092.99 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1046.49 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | 6.14.0-1015.15~24.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1046.49~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1096.105 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1046.52 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | 6.14.0-1014.14~24.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1051.57~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1096.105.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1046.53 | UBUNTU-CVE-2025-38418 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1046.53~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | 6.14.0-1007.7 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1092.101 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1047.50 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | 6.14.0-1018.19~24.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1047.50~22.04.2 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1089.95 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1043.48 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1075.83 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1030.33 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-100.100~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1086.89 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1044.44 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1044.44~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1087.93 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1088.93 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-156.166 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-100.100.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-100.100.1~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1087.88 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1046.49 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1046.49~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1046.49.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1045.45 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1020.20 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1034.34 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | 6.14.0-1014.14 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1090.96 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1043.44 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | 6.14.0-1015.15~24.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1043.44~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1086.89 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1047.51 | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | 6.14.0-34.34.1~24.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-100.100~22.04.1 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-38418 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1023.24 | UBUNTU-CVE-2025-38418 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1056.60 | UBUNTU-CVE-2025-38418 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9dc9507f1880fb6225e3e058cb5219b152cbf198 – before 3562c09feeb8d8e9d102ce6840e8c7d57a7feb5c9dc9507f1880fb6225e3e058cb5219b152cbf198 – before bf876fd9dc2d0c9fff96aef63d4346719f206fc19dc9507f1880fb6225e3e058cb5219b152cbf198 – before 3ee979709e16a83b257bc9a544a7ff71fd445ea99dc9507f1880fb6225e3e058cb5219b152cbf198 – before f4ef928ca504c996f9222eb2c59ac6d6eefd9c759dc9507f1880fb6225e3e058cb5219b152cbf198 – before 6fe9486d709e4a60990843832501ef6556440ca79dc9507f1880fb6225e3e058cb5219b152cbf198 – before bcd241230fdbc6005230f80a4f8646ff5a84f15b |
| Linux | Linux | 5.13 |
References
- https://git.kernel.org/stable/c/3562c09feeb8d8e9d102ce6840e8c7d57a7feb5c
- https://git.kernel.org/stable/c/bf876fd9dc2d0c9fff96aef63d4346719f206fc1
- https://git.kernel.org/stable/c/3ee979709e16a83b257bc9a544a7ff71fd445ea9
- https://git.kernel.org/stable/c/f4ef928ca504c996f9222eb2c59ac6d6eefd9c75
- https://git.kernel.org/stable/c/6fe9486d709e4a60990843832501ef6556440ca7
- https://git.kernel.org/stable/c/bcd241230fdbc6005230f80a4f8646ff5a84f15b
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html