linux-cve-announce - CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025072546-CVE-2025-38419-c07e@gregkh>
Date: Fri, 25 Jul 2025 16:05:48 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38419: remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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 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

The Linux kernel CVE team has assigned CVE-2025-38419 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 5.15.186 with commit c56d6ef2711ee51b54f160ad0f25a381561f0287
	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 6.1.142 with commit 82208ce9505abb057afdece7c62a14687c52c9ca
	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 6.6.95 with commit 9515d74c9d1ae7308a02e8bd4f894eb8137cf8df
	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 6.12.35 with commit 92776ca0ccfe78b9bfe847af206bad641fb11121
	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 6.15.4 with commit 5434d9f2fd68722b514c14b417b53a8af02c4d24
	Issue introduced in 5.13 with commit 10a3d4079eaea06472f1981152e2840e7232ffa9 and fixed in 6.16-rc1 with commit 7692c9fbedd9087dc9050903f58095915458d9b1

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38419
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/remoteproc/remoteproc_core.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/c56d6ef2711ee51b54f160ad0f25a381561f0287
	https://git.kernel.org/stable/c/82208ce9505abb057afdece7c62a14687c52c9ca
	https://git.kernel.org/stable/c/9515d74c9d1ae7308a02e8bd4f894eb8137cf8df
	https://git.kernel.org/stable/c/92776ca0ccfe78b9bfe847af206bad641fb11121
	https://git.kernel.org/stable/c/5434d9f2fd68722b514c14b417b53a8af02c4d24
	https://git.kernel.org/stable/c/7692c9fbedd9087dc9050903f58095915458d9b1