CVE-2026-93272

remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3

N/A
Published: September 24, 2026 at 03:52 PM UTC
Updated: October 30, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

04a89c98810d2dba8187120c07fdb732aa40ca144a89c98810d2dba8187120c7fdb732aa40ca145.15.1856.1.1416.12.316.14.96.156.6.93654c295f9079d2c7875172142022168e34c4e34e65991ea8a6d1e68effdc01d95ebe39f1653f7b7169bb5b3ae348040e385113efba5bdc76396644d08d0d4c11cace475f1b07f98ee3d2bd334590e17bfef1e1487dea81c2b4560e393ba4b0be57e28d01
Vendor states this is fixed in 3dbc90b9c22ea96e37bf55f6011e63b5123ec668 (fixed)
Vendor states this is fixed in bce6b48af3abf7468d12ef4933f21bd8c1d822e9 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.114 (unaffected)
Affected range stops below 6.13, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.18.57 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card