CVE Catalog

CVE-2026-90280

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the qcom qmp-usb PHY driver has a flaw where the runtime suspend callback may run after pm_runtime_enable() but before pm_runtime_forbid(). This causes a dereference of the uninitialized qmp->phy pointer and a crash. It can also occur if a user re-enables runtime-pm via sysfs before the PHY is initialized.

Risk Assessment

Can lead to a kernel panic and denial of service on devices using this Qualcomm PHY driver. Requires local access or specific race conditions, but results in system unavailability.

Recommendation

Update the Linux kernel to a version containing the fix that introduces the qmp->phy_initialized variable. If updating is not possible, avoid manually toggling runtime-pm via sysfs on affected devices.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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 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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS