[CVE-2026-90280][LOW] phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-90280
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend [ Upstream
Commit: 9b28287c5dea7650e6dd317591b9e82b6e145365
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9b28287c5dea7650e6dd317591b9e82b6e145365
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90280
Analysis date: Thu, 17 Sep 2026 17:58:22 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-90280 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90280

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-90280	LOW	https://www.kernelcve.org/list/?q=CVE-2026-90280 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-362;CWE-665;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A race in the Qualcomm QMP USB PHY driver can invoke a runtime suspend or resume callback after runtime PM is enabled but before the qmp phy pointer is initialized. The callback then reads init_count through a NULL pointer and can cause a kernel Oops or crash. The issue can also be triggered when runtime PM is re-enabled through sysfs before PHY initialization completes. For the CVSS the PR:L value is used for the paranoid score because some systems may delegate runtime PM control to a local service or a reduced capability user, while the typical direct sysfs path requires administrative access. AC:H applies because the automatic callback path depends on a small timing window. The issue is local, hardware and driver specific, and is not reachable through network traffic. Impact is denial of service only. The visible primitive is a NULL pointer invalid read with no supported UAF, out of bounds write, information disclosure, or privilege escalation path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)  SKIP CVE-2026-90280 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	DANGER USB INIT SIMPLEFIX HARDWARE LINUS MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 0
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* No floor or cap applies.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Reliable kernel crash or strong DoS. The commit directly states that dereferencing the uninitialized `qmp->phy` pointer causes a crash.
* -1 Hard or unreliable race. The automatic runtime-PM path exists only in the explicitly described small window between `pm_runtime_enable()` and `pm_runtime_forbid()`. The sysfs path must also act before PHY initialization completes.
* No UAF or lifetime-corruption points. The pointer has not yet been initialized rather than having been freed.
* No corruption points. The demonstrated operation is a NULL-based invalid read of `init_count`, with no write, object reuse, or secondary corruption sink.
* No local-unprivileged point. Write access to the relevant runtime-PM sysfs attribute by an ordinary user is not established.
* No host-admin penalty. Administrative access may be needed for the sysfs route, but the supplied evidence does not establish the complete privilege boundary, and the automatic PM race needs no userspace write.
* No hardware penalty. A Qualcomm QMP USB PHY is required, but the evidence does not establish rare hardware or a need for attacker physical access.
* No extra Availability point. It would duplicate the same kernel Oops or crash.
* Controlled reclaim, arbitrary write, disclosure, privilege escalation, and remote reachability are not demonstrated.

3. Reachability analysis

The race can occur automatically when the PM callback runs during driver initialization. A user can also attempt to trigger it by re-enabling runtime PM through the device sysfs attribute before initialization finishes, but the supplied evidence does not establish whether a below-host-admin actor can write that attribute.

The operation concerns a host physical platform device and is not namespace-scoped. An attacker-created user or network namespace does not provide control over this PHY or its runtime-PM sysfs state. The affected Qualcomm QMP USB hardware and driver must be present. No network trigger exists. The automatic path is a narrow initialization race and is not shown to be cheaply repeatable by an unprivileged actor.

4. Primitive and severity interpretation

The exact primitive is a read through an uninitialized NULL `qmp->phy` pointer in the runtime suspend or resume callback. This is neither a stale post-lifetime object nor fixed stale storage. There is no first release, surviving dangling reference, or second lifetime/refcount mutation.

The issue is CLASS_C because the demonstrated behavior is an invalid dereference and crash without an independently useful corruption primitive. The practical consequence is local host denial of service on affected hardware. Stronger consequences such as UAF exploitation, kernel memory modification, information disclosure, or privilege escalation are unsupported.

ImportantCandidate is NO because no Class A or meaningful Class B primitive exists. AutoDowngradeAllowed is YES because the established result is a constrained initialization-time NULL dereference with no unresolved corruption or security-boundary mechanism.

5. One-sentence report phrase

A narrow initialization race in the Qualcomm QMP USB PHY driver can make a runtime PM callback read through an uninitialized NULL PHY pointer and crash the kernel, with no demonstrated memory corruption or privilege escalation primitive.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a hardware-specific, timing-constrained NULL-pointer read and DoS without UAF, writable corruption, disclosure, or boundary-bypass evidence.

7. Call-site confidence

Call-site confidence: high

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend [ Upstream
Commit: 9b28287c5dea7650e6dd317591b9e82b6e145365
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9b28287c5dea7650e6dd317591b9e82b6e145365

Changed files:
  drivers/phy/qualcomm/phy-qcom-qmp-usb.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9b28287c5dea7650e6dd317591b9e82b6e145365

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-90280 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90280

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 0

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).