Answer in brief
CVE-2025-71193 records a Unknown severity vulnerability in phy: qcom-qusb2: Fix NULL pointer dereference on early 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 4.17 | Not reported |
| Linux/Linuxgeneric | >=891a96f65ac3b12883ddbc6d1a9adf6e54dc903c <f8a30ff99ae45d368737993961f7c334c76af5fa || >=891a96f65ac3b12883ddbc6d1a9adf6e54dc903c <beba460a299150b5d8dcbe3474a8f4bdf0205180 || >=891a96f65ac3b12883ddbc6d1a9adf6e54dc903c <d50a9b7fd07296a1ab81c49ceba14cae3d31df86 || >=891a96f65ac3b12883ddbc6d1a9adf6e54dc903c <4ac15caa27ff842b068a54f1c6a8ff8b31f658e7 || >=891a96f65ac3b12883ddbc6d1a9adf6e54dc903c <1ca52c0983c34fca506921791202ed5bdafd5306 | f8a30ff99ae45d368737993961f7c334c76af5fa, beba460a299150b5d8dcbe3474a8f4bdf0205180, d50a9b7fd07296a1ab81c49ceba14cae3d31df86, 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7, 1ca52c0983c34fca506921791202ed5bdafd5306 |
Published upstream
Feb 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend Enabling runtime PM before attaching the QPHY instance as driver data can lead to a NULL pointer dereference in runtime PM callbacks that expect valid driver data. There is a small window where the suspend callback may run after PM runtime enabling and before runtime forbid. This causes a sporadic crash during boot: ``` Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a1 [...] CPU: 0 UID: 0 PID: 11 Comm: kworker/0:1 Not tainted 6.16.7+ #116 PREEMPT Workqueue: pm pm_runtime_work pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : qusb2_phy_runtime_suspend+0x14/0x1e0 [phy_qcom_qusb2] lr : pm_generic_runtime_suspend+0x2c/0x44 [...] ``` Attach the QPHY instance as driver data before enabling runtime PM to prevent NULL pointer dereference in runtime PM callbacks. Reorder pm_runtime_enable() and pm_runtime_forbid() to prevent a short window where an unnecessary runtime suspend can occur. Use the devres-managed version to ensure PM runtime is symmetrically disabled during driver removal for proper cleanup.
Quoted source text, attributed separately from HOL analysis.