VDB

CVE-2025-38419

CVE-2025-38419 PUBLISHED

Reported by linux · Published July 25, 2025

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: [<00000000f949fe18>] slab_post_alloc_hook+0x98/0x37c [<00000000adbfb3e7>] __kmem_cache_alloc_node+0x138/0x2e0 [<00000000521c0345>] kmalloc_trace+0x40/0x158 [<000000004e330a49>] rproc_mem_entry_init+0x60/0xf8 [<000000002815755e>] imx_rproc_prepare+0xe0/0x180 [<0000000003f61b4e>] rproc_boot+0x2ec/0x528 [<00000000e7e994ac>] rproc_add+0x124/0x17c [<0000000048594076>] imx_rproc_probe+0x4ec/0x5d4 [<00000000efc298a1>] platform_probe+0x68/0xd8 [<00000000110be6fe>] really_probe+0x110/0x27c [<00000000e245c0ae>] __driver_probe_device+0x78/0x12c [<00000000f61f6f5e>] driver_probe_device+0x3c/0x118 [<00000000a7874938>] __device_attach_driver+0xb8/0xf8 [<0000000065319e69>] bus_for_each_drv+0x84/0xe4 [<00000000db3eb243>] __device_attach+0xfc/0x18c [<0000000072e4e1a4>] device_initial_probe+0x14/0x20

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxc56d6ef2711ee51b54f160ad0f25a381561f0287, 9515d74c9d1ae7308a02e8bd4f894eb8137cf8df, 92776ca0ccfe78b9bfe847af206bad641fb11121, 82208ce9505abb057afdece7c62a14687c52c9ca, 7692c9fbedd9087dc9050903f58095915458d9b1, 5434d9f2fd68722b514c14b417b53a8af02c4d24, 5.13

Affected products

VendorProductVersions
LinuxLinux10a3d4079eaea06472f1981152e2840e7232ffa9, 10a3d4079eaea06472f1981152e2840e7232ffa9, 10a3d4079eaea06472f1981152e2840e7232ffa9
LinuxLinux5.13, 0, 5.15.186
LinuxLinux0, 5.15.186, 6.1.142
linuxlinux_kernel5.13, 5.13, 5.13

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-38419
vulnetix vdb fixes CVE-2025-38419

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-38419/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›