CVE-2026-90282

phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.6e464a3180a43b6596bd267f9f274e1793bfb8150
Vendor states this is fixed in 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5 (fixed)
Vendor states this is fixed in 29449ce1f5958e36df80318878016e3ecac26b40 (fixed)
Vendor states this is fixed in 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd (fixed)
Vendor states this is fixed in 602059c5128a78857ca92bd22791ab640185e381 (fixed)
Vendor states this is fixed in 8e3687f7e18fe84372e86875709d56c37e7525a8 (fixed)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card