CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 1ca52c0983c34fca506921791202ed5bdafd5306, 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7, beba460a299150b5d8dcbe3474a8f4bdf0205180.
Low priority for now. Upgrade to Linux Linux 1ca52c0983c34fca506921791202ed5bdafd5306, 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7, beba460a299150b5d8dcbe3474a8f4bdf0205180 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 4, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.17affected
- 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c and later · before f8a30ff99ae45d368737993961f7c334c76af5faaffected · git
- 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c and later · before beba460a299150b5d8dcbe3474a8f4bdf0205180affected · git
- 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c and later · before d50a9b7fd07296a1ab81c49ceba14cae3d31df86affected · git
- 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c and later · before 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7affected · git
- 891a96f65ac3b12883ddbc6d1a9adf6e54dc903c and later · before 1ca52c0983c34fca506921791202ed5bdafd5306affected · git
- before 4.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.122 and later · up to and including 6.6.*not affected · semver
- 6.12.67 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-23058Feb 4, 2026 · can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak0Monitor
- ← EarlierCVE-2026-23059Feb 4, 2026 · scsi: qla2xxx: Sanitize payload size to prevent member overflow0Monitor
- Later →CVE-2025-71194Feb 4, 2026 · btrfs: fix deadlock in wait_current_trans() due to ignored transaction type0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ca52c0983c34fca506921791202ed5bdafd5306 | Vendor (CNA) |
| Linux Linux | 4ac15caa27ff842b068a54f1c6a8ff8b31f658e7 | Vendor (CNA) |
| Linux Linux | beba460a299150b5d8dcbe3474a8f4bdf0205180 | Vendor (CNA) |
| Linux Linux | d50a9b7fd07296a1ab81c49ceba14cae3d31df86 | Vendor (CNA) |
| Linux Linux | f8a30ff99ae45d368737993961f7c334c76af5fa | Vendor (CNA) |
| debian:linux | 6.12.69-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.