clk: mediatek: Do a runtime PM get on controllers during probe
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 165d226472575b213dd90dfda19d1605dd7c19a8, Kernel 2f7b1d8b5505efb0057cd1ab85fca206063ea4c3, Kernel b62ed25feb342eab052822eff0c554873799a4f5 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: Do a runtime PM get on controllers during probe mt8183-mfgcfg has a mutual dependency with genpd during the probing stage, which leads to a deadlock in the following call stack: CPU0: genpd_lock --> clk_prepare_lock genpd_power_off_work_fn() genpd_lock() generic_pm_domain::power_off() clk_unprepare() clk_prepare_lock() CPU1: clk_prepare_lock --> genpd_lock clk_register() __clk_core_init() clk_prepare_lock() clk_pm_runtime_get() genpd_lock() Do a runtime PM get at the probe function to make sure clk_register() won't acquire the genpd lock. Instead of only modifying mt8183-mfgcfg, do this on all mediatek clock controller probings because we don't believe this would cause any regression. Verified on MT8183 and MT8192 Chromebooks.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.2, >=acddfc2c261b3653ab1c1b567a427299bac20d31 <165d226472575b213dd90dfda19d1605dd7c19a8, >=acddfc2c261b3653ab1c1b567a427299bac20d31 <2f7b1d8b5505efb0057cd1ab85fca206063ea4c3, >=acddfc2c261b3653ab1c1b567a427299bac20d31 <b62ed25feb342eab052822eff0c554873799a4f5, >=acddfc2c261b3653ab1c1b567a427299bac20d31 <c0dcd5c072e2a3fff886f673e6a5d9bf8090c4cc | 165d226472575b213dd90dfda19d1605dd7c19a8, 2f7b1d8b5505efb0057cd1ab85fca206063ea4c3, b62ed25feb342eab052822eff0c554873799a4f5, c0dcd5c072e2a3fff886f673e6a5d9bf8090c4cc |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket