Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93272remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 36 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8d0d4c11cace475f1b07f98ee3d2bd334590e17b – < d5deaa0b6d91b1063055415fc53f75c40c2a077d
    • affected fef1e1487dea81c2b4560e393ba4b0be57e28d01 – < 7abab59d6c99ba2b8101d6f44ad25159b1510724
    • affected 69bb5b3ae348040e385113efba5bdc76396644d0 – < e572cbb513cde53d90fb4729cad75056cd647ce3
    • affected 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 – < 2e7e39bb81913feaac463b7add46bafdca06fbde
    • affected 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 – < bce6b48af3abf7468d12ef4933f21bd8c1d822e9
    • affected 65991ea8a6d1e68effdc01d95ebe39f1653f7b71 – < 3dbc90b9c22ea96e37bf55f6011e63b5123ec668
    • affected 654c295f9079d2c7875172142022168e34c4e34e
    • affected 04a89c98810d2dba8187120c07fdb732aa40ca14
    • affected 6.1.141 – < 6.1.191
    • affected 6.6.93 – < 6.6.160
    • affected 6.12.31 – < 6.12.114
    • affected 5.15.185 – < 5.16
    • affected 6.14.9 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93272 badge
[![CVE-2026-93272](https://cveledger.app/badge/CVE-2026-93272.svg)](https://cveledger.app/cve/CVE-2026-93272)

Record last updated .