CVE-2025-38418
- Published: 2025-07-25T14:15:33.603
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:
[] slab_post_alloc_hook+0x98/0x3fc
[] __kmem_cache_alloc_node+0x13c/0x230
[] __kmalloc_node_track_caller+0x5c/0x260
[] kmemdup+0x34/0x60
[] rproc_boot+0x35c/0x56c
[] rproc_add+0x124/0x17c
[] imx_rproc_probe+0x4ec/0x5d4
[] platform_probe+0x68/0xd8
[] really_probe+0x110/0x27c
[] __driver_probe_device+0x78/0x12c
[] driver_probe_device+0x3c/0x118
[] __device_attach_driver+0xb8/0xf8
[] bus_for_each_drv+0x84/0xe4
[] __device_attach+0xfc/0x18c
[] device_initial_probe+0x14/0x20
[] bus_probe_device+0xb0/0xb4
unreferenced object 0xffff0000864c9690 (size 16):
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2025-38418
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, […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
Vulnerability Timeline
CVE details first published to NVD database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.