CVE-2025-71193 Details
Description
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.
A vulnerability in the Linux kernel's QCOM QUSB2 PHY driver can lead to a NULL pointer dereference. This issue arises when runtime power management (PM) is enabled before the QPHY instance is attached as driver data. As a result, PM callbacks that rely on valid driver data can cause a sporadic crash during boot, with the system unable to handle the NULL pointer dereference. The problem occurs because there is a brief window where the suspend callback can execute after PM runtime is enabled and before it is forbidden, leading to a crash.
The vulnerability has been addressed by modifying the driver to attach the QPHY instance as driver data before enabling runtime power management. This change prevents the NULL pointer dereference in PM callbacks. Additionally, the order of the PM runtime enable and forbid commands has been adjusted to eliminate the brief window where an unnecessary runtime suspend could occur. The updated driver version should be used to ensure proper handling of power management and to avoid this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Feb 4, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1ca52c0983c34fca506921791202ed5bdafd5306 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/4ac15caa27ff842b068a54f1c6a8ff8b31f658e7 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/beba460a299150b5d8dcbe3474a8f4bdf0205180 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d50a9b7fd07296a1ab81c49ceba14cae3d31df86 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f8a30ff99ae45d368737993961f7c334c76af5fa | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
| qcom-qusb2 | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 4, 2026 | New CVE Received | kernel.org |
Volerion