phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5, Kernel 29449ce1f5958e36df80318878016e3ecac26b40, Kernel 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd and 2 more.
In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend There is a small window where the runtime suspend callback may run after pm_runtime_enable() and before pm_runtime_forbid(). In this case, a crash occurs because runtime suspend/resume dereferences qmp->phy pointer, which is not yet initialized: `if (!qmp->phy->init_count) {` This can also happen if user re-enables runtime-pm via the sysfs attribute before qmp phy is initialized. Similarly to other qcom phy drivers, introduce a qmp->phy_initialized variable that can be used to avoid relying on the possibly uninitialized phy pointer.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.6, >=e464a3180a43b6596bd267f9f274e1793bfb8150 <0f9789d1b63e7d9f868ac9c29564339a4c03ceb5, >=e464a3180a43b6596bd267f9f274e1793bfb8150 <29449ce1f5958e36df80318878016e3ecac26b40, >=e464a3180a43b6596bd267f9f274e1793bfb8150 <52ad86ea5f98d29a7a29d9ba12e24276c6e30acd, >=e464a3180a43b6596bd267f9f274e1793bfb8150 <602059c5128a78857ca92bd22791ab640185e381, >=e464a3180a43b6596bd267f9f274e1793bfb8150 <8e3687f7e18fe84372e86875709d56c37e7525a8 | 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5, 29449ce1f5958e36df80318878016e3ecac26b40, 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd, 602059c5128a78857ca92bd22791ab640185e381, 8e3687f7e18fe84372e86875709d56c37e7525a8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket