https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 15:42:17 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-93272 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-93272 https://vulnerability.circl.lu/vuln/fkie_cve-2026-93272 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3</p> <p>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.</p> <p>This showed up as a difference between GCC- and LLVM-compiled kernels on SDM632 devices, where only with LLVM one would get the &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3</p> <p>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.</p> <p>This showed up as a difference between GCC- and LLVM-compiled kernels on SDM632 devices, where only with LLVM one would get the &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-93272 https://vulnerability.circl.lu/vuln/ghsa-4gpg-4875-c7gx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3</p> <p>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.</p> <p>This showed up as a difference between GCC- and LLVM-compiled kernels on SDM632 devices, where only with LLVM one would get the &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3</p> <p>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.</p> <p>This showed up as a difference between GCC- and LLVM-compiled kernels on SDM632 devices, where only with LLVM one would get the &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> https://vulnerability.circl.lu/vuln/ghsa-4gpg-4875-c7gx https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93272 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>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 &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>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 &#34;regulator request with no identifier&#34; error, because the out-of-bounds memory ended up being zeroed. Fix by skipping the increment when there are more power domains than regulators.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93272 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579