Danilo Krummrich 964a44a990 rpmsg: use generic driver_override infrastructure ...

[ Upstream commit 55ced13c42 ]

When a driver is probed through __driver_attach(), the bus' match()
callback is called without the device lock held, thus accessing the
driver_override field without a lock, which can cause a UAF.

Fix this by using the driver-core driver_override infrastructure taking
care of proper locking internally.

Note that calling match() from __driver_attach() without the device lock
held is intentional. [1]

Link: https://lore.kernel.org/driver-core/DGRGTIRHA62X.3RY09D9SOK77P@kernel.org/ [1]
Reported-by: Gui-Dong Han <hanguidong02@gmail.com>
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220789
Fixes: e950604782 ("rpmsg: Introduce a driver override mechanism")
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://patch.msgid.link/20260505133935.3772495-5-dakr@kernel.org
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2026-07-24 16:03:05 +02:00

..

Kconfig

…

Makefile

…

mtk_rpmsg.c

…

qcom_glink_native.c

rpmsg: use generic driver_override infrastructure

2026-07-24 16:03:05 +02:00

qcom_glink_native.h

…

qcom_glink_rpm.c

…

qcom_glink_smem.c

…

qcom_glink_ssr.c

…

qcom_smd.c

…

rpmsg_char.c

rpmsg: char: Fix use-after-free on probe error path

2026-07-04 13:42:27 +02:00

rpmsg_char.h

…

rpmsg_core.c

rpmsg: use generic driver_override infrastructure

2026-07-24 16:03:05 +02:00

rpmsg_ctrl.c

…

rpmsg_internal.h

…

rpmsg_ns.c

…

virtio_rpmsg_bus.c

rpmsg: use generic driver_override infrastructure

2026-07-24 16:03:05 +02:00