spmi: mediatek: Fix UAF on device remove
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:
spmi: mediatek: Fix UAF on device remove
The pmif driver data that contains the clocks is allocated along with spmi_controller. On device remove, spmi_controller will be freed first, and then devres , including the clocks, will be cleanup. This leads to UAF because putting the clocks will access the clocks in the pmif driver data, which is already freed along with spmi_controller.
This can be reproduced by enabling DEBUG_TEST_DRIVER_REMOVE and building the kernel with KASAN.
Fix the UAF issue by using unmanaged clk_bulk_get() and putting the clocks before freeing spmi_controller.
From the CVE record · Linux
The Linux kernel's MediaTek SPMI pmif driver has a use-after-free during device removal: clock cleanup accesses driver data after the SPMI controller has been freed. It can be reproduced with DEBUG_TEST_DRIVER_REMOVE enabled and a KASAN-enabled kernel. The input does not establish an attacker path, authentication requirement, or user interaction requirement.
Engineers running Linux kernels with the MediaTek SPMI pmif driver should check their kernels; affected versions are not specified.