CVE-2026-90280: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend
In the Linux kernel, the following vulnerability has been resolved:
phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend
There is a small window where the runtime suspend callback may run after pmruntimeenable() and before pmruntimeforbid(). In this case, a crash occurs because runtime suspend/resume dereferences qmp->phy pointer, which is not yet initialized: if (!qmp->phy->initcount) {
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->phyinitialized variable that can be used to avoid relying on the possibly uninitialized phy pointer.
Affected Software
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue applies to Linux systems using the Qualcomm QMP USB PHY driver. The affected condition is during PHY initialization when runtime power-management callbacks can run before the PHY pointer is initialized.
What conditions trigger the crash?
A crash can occur if runtime suspend runs after pm_runtime_enable() but before pm_runtime_forbid(). It can also occur if runtime PM is re-enabled through its sysfs attribute before QMP PHY initialization completes.
Does the report identify an attacker-controlled exploitation path?
No. The available information describes a NULL-pointer dereference and crash caused by runtime power-management timing or premature runtime-PM re-enablement, but does not identify a remote or local attacker-controlled vector.