CVE-2025-38419
- Published: 2025-07-25T14:15:33.727
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach()
When rproc->state = RPROC_DETACHED and rproc_attach() is used
to attach to the remote processor, if rproc_handle_resources()
returns a failure, the resources allocated by imx_rproc_prepare()
should be released, otherwise the following memory leak will occur.
Since almost the same thing is done in imx_rproc_prepare() and
rproc_resource_cleanup(), Function rproc_resource_cleanup() is able
to deal with empty lists so it is better to fix the “goto” statements
in rproc_attach(). replace the “unprepare_device” goto statement with
“clean_up_resources” and get rid of the “unprepare_device” label.
unreferenced object 0xffff0000861c5d00 (size 128):
comm “kworker/u12:3”, pid 59, jiffies 4294893509 (age 149.220s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
00 00 02 88 00 00 00 00 00 00 10 00 00 00 00 00 …………
backtrace:
[] slab_post_alloc_hook+0x98/0x37c
[] __kmem_cache_alloc_node+0x138/0x2e0
[] kmalloc_trace+0x40/0x158
[] rproc_mem_entry_init+0x60/0xf8
[] imx_rproc_prepare+0xe0/0x180
[] rproc_boot+0x2ec/0x528
[] 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
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-38419
Description: In the Linux kernel, the following vulnerability has been resolved: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach() When rproc->state = RPROC_DETACHED and rproc_attach() is used to attach to the remote processor, if rproc_handle_resources() returns a failure, the resources allocated by imx_rproc_prepare() should be released, otherwise the following memory leak will occur. Since […]
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.