diff options
| author | Danilo Krummrich <dakr@kernel.org> | 2026-03-03 12:53:21 +0100 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-03-17 20:30:57 +0100 |
| commit | 2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d (patch) | |
| tree | 64913e7184ba0cd8ebc40838934425f92c0bfaab /tools/perf/scripts/python/bin | |
| parent | c5f60e3f07b6609562d21efda878e83ce8860728 (diff) | |
| download | kernel-2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d.tar.gz | |
driver core: platform: use generic driver_override infrastructure
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: 3d713e0e382e ("driver core: platform: add device binding path 'driver_override'")
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://patch.msgid.link/20260303115720.48783-5-dakr@kernel.org
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions