CVE-2025-38418
remoteproc: core: Release rproc->clean_table after rproc_attach() fails
Reported by linux · Published July 25, 2025
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):
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.15.4, 6.12.35, 6.6.95, 6.1.142, 5.15.186 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9dc9507f1880fb6225e3e058cb5219b152cbf198, 9dc9507f1880fb6225e3e058cb5219b152cbf198, 9dc9507f1880fb6225e3e058cb5219b152cbf198 |
| Linux | Linux | 5.13, 0, 5.15.186 |
| linux | linux_kernel | 5.13, 5.13, 5.13 |
| Linux | Linux | 9dc9507f1880fb6225e3e058cb5219b152cbf198, 9dc9507f1880fb6225e3e058cb5219b152cbf198, 9dc9507f1880fb6225e3e058cb5219b152cbf198 |
Timeline
- Jul 25, 2025 CVE Published
- Jul 26, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (25 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (243 in total, the first dated here)
- Mar 29, 2026 Security Advisory (260 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
- Oct 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38418
vulnetix vdb fixes CVE-2025-38418
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38418/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart