remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 · < 3dbc90b9c22ea96e37bf55f6011e63b5123ec668| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The qcom_wcnss remoteproc driver can shift a pointer past the end of an array on pronto-v3 platforms that lack power-domain regulators. This caused a regulator-request error on LLVM-compiled kernels on SDM632 devices. The input does not describe an attacker capability or access conditions.
Engineers running Linux kernels on affected pronto-v3 platforms, including SDM632 devices, should check; affected versions are not specified.