platform/wmi: use generic driver_override infrastructure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
platform/wmi: 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]
From the CVE record · Linux
The Linux kernel's platform/wmi driver matching can access the driver_override field without a device lock, causing a use-after-free. The input does not specify how an attacker could trigger this or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their systems; affected versions are not specified.