CVE-2026-93272: remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 2e7e39bb81913feaac463b7add46bafdca06fbde, 3dbc90b9c22ea96e37bf55f6011e63b5123ec668, 5.16.
Low priority for now. Upgrade to Linux Linux 2e7e39bb81913feaac463b7add46bafdca06fbde, 3dbc90b9c22ea96e37bf55f6011e63b5123ec668, 5.16 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: remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3 The changes introduced to handle single power domain platforms have swapped the info pointer increment from num_pd_vregs to num_pds, which would shift the info pointer past the end of the array for pronto-v3, which does not list power domain regulators in vregs. This showed up as a difference between GCC- and LLVM-compiled kernels on SDM632 devices, where only with LLVM one would get the "regulator request with no identifier" error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.
- Published
- Sep 24, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 8th 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.1%
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
- 654c295f9079d2c7875172142022168e34c4e34e, 04a89c98810d2dba8187120c07fdb732aa40ca14, 6.15affected
- 8d0d4c11cace475f1b07f98ee3d2bd334590e17b and later · before d5deaa0b6d91b1063055415fc53f75c40c2a077daffected · git
- fef1e1487dea81c2b4560e393ba4b0be57e28d01 and later · before 7abab59d6c99ba2b8101d6f44ad25159b1510724affected · git
- 69bb5b3ae348040e385113efba5bdc76396644d0 and later · before e572cbb513cde53d90fb4729cad75056cd647ce3affected · git
- 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 and later · before 2e7e39bb81913feaac463b7add46bafdca06fbdeaffected · git
- 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 and later · before bce6b48af3abf7468d12ef4933f21bd8c1d822e9affected · git
- 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 and later · before 3dbc90b9c22ea96e37bf55f6011e63b5123ec668affected · git
- 6.1.141 and later · before 6.1.191affected · semver
- 6.6.93 and later · before 6.6.160affected · semver
- 6.12.31 and later · before 6.12.114affected · 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.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-93270Sep 24, 2026 · bpf: Disallow interpreter fallback for BPF_ADDR_PERCPU insn0Monitor
- ← EarlierCVE-2026-93271Sep 24, 2026 · wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate0Monitor
- Later →CVE-2026-93273Sep 24, 2026 · regulator: tps6594: Fix device node reference leaks in multiphase loop0Monitor
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 | 2e7e39bb81913feaac463b7add46bafdca06fbde | Vendor (CNA) |
| Linux Linux | 3dbc90b9c22ea96e37bf55f6011e63b5123ec668 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.12.114 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 7abab59d6c99ba2b8101d6f44ad25159b1510724 | Vendor (CNA) |
| Linux Linux | bce6b48af3abf7468d12ef4933f21bd8c1d822e9 | Vendor (CNA) |
| Linux Linux | d5deaa0b6d91b1063055415fc53f75c40c2a077d | Vendor (CNA) |
| Linux Linux | e572cbb513cde53d90fb4729cad75056cd647ce3 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 (5 more)Show less
- git.kernel.org/stable/c/3dbc90b9c22ea96e37bf55f6011e63b5123ec668
- git.kernel.org/stable/c/7abab59d6c99ba2b8101d6f44ad25159b1510724
- git.kernel.org/stable/c/bce6b48af3abf7468d12ef4933f21bd8c1d822e9
- git.kernel.org/stable/c/d5deaa0b6d91b1063055415fc53f75c40c2a077d
- git.kernel.org/stable/c/e572cbb513cde53d90fb4729cad75056cd647ce3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.