Description
In the Linux kernel, the following vulnerability has been resolved: 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]
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d Patch
- git.kernel.org/stable/c/7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1 Patch
- git.kernel.org/stable/c/9a6086d2a828dd2ff74cf9abcae456670febd71f Patch
- git.kernel.org/stable/c/edee7ee5a14c3b33f6d54641f5af5c5e9180992d Patch
- git.kernel.org/stable/c/492349e5e4a369a8b62781100a3ade470bf1ce6b
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 3 · as of 13 November 2026
- CWE
- CWE-416
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.