CVE-2026-93272 json
remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
published 2026-09-24 45 d ago modified 2026-10-30 10 d ago also EUVD-2026-86144
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.16, 6.1.191, 6.6.160, 6.12.114, 6.15, 6.18.57, 7.2.6, 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-93272
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-93272
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.9-1.1
opensuse advisories openSUSE-SU-2026:12074-1
- git.kernel.org/stable/c/d5deaa0b6d91b1063055415fc53f75c40c2a077d commit
- git.kernel.org/stable/c/7abab59d6c99ba2b8101d6f44ad25159b1510724 commit
- git.kernel.org/stable/c/e572cbb513cde53d90fb4729cad75056cd647ce3 commit
- git.kernel.org/stable/c/2e7e39bb81913feaac463b7add46bafdca06fbde commit
- git.kernel.org/stable/c/bce6b48af3abf7468d12ef4933f21bd8c1d822e9 commit
- git.kernel.org/stable/c/3dbc90b9c22ea96e37bf55f6011e63b5123ec668 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93272 updated cvss 5.5
kernel: remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/d5deaa0b6d91b1063055415fc53f75c40c2a077d
- git.kernel.org /stable/c/7abab59d6c99ba2b8101d6f44ad25159b1510724
- git.kernel.org /stable/c/e572cbb513cde53d90fb4729cad75056cd647ce3
- git.kernel.org /stable/c/2e7e39bb81913feaac463b7add46bafdca06fbde
- git.kernel.org /stable/c/bce6b48af3abf7468d12ef4933f21bd8c1d822e9
- git.kernel.org /stable/c/3dbc90b9c22ea96e37bf55f6011e63b5123ec668
Sources
- CVE List CVE-2026-93272
- NVD CVE-2026-93272
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.