Bug 2536443 (CVE-2026-90282) - CVE-2026-90282 kernel: phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend
Summary: CVE-2026-90282 kernel: phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on ...
Keywords:
Status: NEW
Alias: CVE-2026-90282
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 17:55 UTC by OSIDB Bzimport
Modified: 2026-10-13 13:49 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 17:55:34 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.