CVE-2026-93272
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..
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 65991ea8a6d1e68effdc01d95ebe39f1653f7b71, < bce6b48af3abf7468d12ef4933f21bd8c1d822e9; >= 65991ea8a6d1e68effdc01d95ebe39f1653f7b71, < 3dbc90b9c22ea96e37bf55f6011e63b5123ec668; 654c295f9079d2c7875172142022168e34c4e34e; 8d0d4c11cace475f1b07f98ee3d2bd334590e17b; fef1e1487dea81c2b4560e393ba4b0be57e28d01; 69bb5b3ae348040e385113efba5bdc76396644d0; 04a89c98810d2dba8187120c07fdb732aa40ca14; >= 5.15.185, < 5.16; >= 6.1.141, < 6.2; >= 6.6.93, < 6.7; >= 6.12.31, < 6.13; >= 6.14.9, < 6.15 |
| Linux | Linux | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93272?
How severe is CVE-2026-93272?
How do I fix CVE-2026-93272?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93267In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93268In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93269In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9327IBM WebSphere Application Server 9.0, and 8.5 could allow an…8.1
- CVE-2026-93270In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93271In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93273In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93274In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93275In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93276In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93277In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93278In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93272?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
