Strix
74.6K

CVE-2026-93272

UnknownEPSS 0.19%

Last modified

CVE-2026-93272 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.19% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.19%

8.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8d0d4c11cace475f1b07f98ee3d2bd334590e17b, < d5deaa0b6d91b1063055415fc53f75c40c2a077d; >= fef1e1487dea81c2b4560e393ba4b0be57e28d01, < 7abab59d6c99ba2b8101d6f44ad25159b1510724; >= 69bb5b3ae348040e385113efba5bdc76396644d0, < e572cbb513cde53d90fb4729cad75056cd647ce3; >= 65991ea8a6d1e68effdc01d95ebe39f1653f7b71, < 2e7e39bb81913feaac463b7add46bafdca06fbde; >= 65991ea8a6d1e68effdc01d95ebe39f1653f7b71, < bce6b48af3abf7468d12ef4933f21bd8c1d822e9; >= 65991ea8a6d1e68effdc01d95ebe39f1653f7b71, < 3dbc90b9c22ea96e37bf55f6011e63b5123ec668; 654c295f9079d2c7875172142022168e34c4e34e; 04a89c98810d2dba8187120c07fdb732aa40ca14; >= 6.1.141, < 6.1.191; >= 6.6.93, < 6.6.160; >= 6.12.31, < 6.12.114; >= 5.15.185, < 5.16; >= 6.14.9, < 6.15
LinuxLinux6.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93272?
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.
How severe is CVE-2026-93272?
Severity scoring for CVE-2026-93272 is pending analysis. The EPSS model estimates a 0.19% probability of exploitation in the next 30 days.
How do I fix CVE-2026-93272?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93272?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST