Skip to main content
VulnerabilityPublished Updated

CVE-2025-71193: Linux kernel · phy: qcom-qusb2: Fix NULL pointer dereference on early suspend

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-71193

Not known to be exploited · fixed in f8a30ff99ae45d368737993961f7c334c76af5fa : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
Patch
Available – fixed in f8a30ff99ae45d368737993961f7c334c76af5fa, d50a9b7fd07296a1ab81c49ceba14cae3d31df86, beba460a299150b5d8dcbe3474a8f4bdf0205180 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c, < f8a30ff99ae45d368737993961f7c334c76af5fa
Fixed in
  • f8a30ff99ae45d368737993961f7c334c76af5fa
LinuxLinuxAffected
  • ≥ 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c, < d50a9b7fd07296a1ab81c49ceba14cae3d31df86
Fixed in
  • d50a9b7fd07296a1ab81c49ceba14cae3d31df86
LinuxLinuxAffected
  • ≥ 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c, < beba460a299150b5d8dcbe3474a8f4bdf0205180
Fixed in
  • beba460a299150b5d8dcbe3474a8f4bdf0205180
LinuxLinuxAffected
  • ≥ 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c, < 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7
Fixed in
  • 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7
LinuxLinuxAffected
  • ≥ 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c, < 1ca52c0983c34fca506921791202ed5bdafd5306
Fixed in
  • 1ca52c0983c34fca506921791202ed5bdafd5306
LinuxLinuxAffected
  • =4.17
Fixed in–

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.

References

Community reviews

Loading reviews…