phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend (CVE-2026-90282) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90282

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

Answer in brief

CVE-2026-90282 records a Unknown severity vulnerability in phy: qcom: qmp-usb-legacy: Fix possible NULL-deref on early runtime suspend. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=e464a3180a43b6596bd267f9f274e1793bfb8150 <602059c5128a78857ca92bd22791ab640185e381 \|\| >=e464a3180a43b6596bd267f9f274e1793bfb8150 <29449ce1f5958e36df80318878016e3ecac26b40 \|\| >=e464a3180a43b6596bd267f9f274e1793bfb8150 <52ad86ea5f98d29a7a29d9ba12e24276c6e30acd \|\| >=e464a3180a43b6596bd267f9f274e1793bfb8150 <0f9789d1b63e7d9f868ac9c29564339a4c03ceb5 \|\| >=e464a3180a43b6596bd267f9f274e1793bfb8150 <8e3687f7e18fe84372e86875709d56c37e7525a8	602059c5128a78857ca92bd22791ab640185e381, 29449ce1f5958e36df80318878016e3ecac26b40, 52ad86ea5f98d29a7a29d9ba12e24276c6e30acd, 0f9789d1b63e7d9f868ac9c29564339a4c03ceb5, 8e3687f7e18fe84372e86875709d56c37e7525a8
Linux/Linuxgeneric	6.6	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 602059c5128a78857ca92bd22791ab640185e381 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.