https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:16:17 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-12206 bdu:2025-12206 https://cve.radiocsirt.org/vuln/bdu:2025-12206 https://cve.radiocsirt.org/vuln/bell-cve-2024-58084 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-58084 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/euvd-2026-313976 EUVD-2026-313976 https://cve.radiocsirt.org/vuln/euvd-2026-313976 https://cve.radiocsirt.org/vuln/fkie_cve-2024-58084 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</p> <p>Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly.</p> <p>Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it.</p> <p>Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</p> <p>Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly.</p> <p>Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it.</p> <p>Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-58084 https://cve.radiocsirt.org/vuln/ghsa-q37x-r635-xf49 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</p> <p>Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly.</p> <p>Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it.</p> <p>Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</p> <p>Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly.</p> <p>Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it.</p> <p>Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> https://cve.radiocsirt.org/vuln/ghsa-q37x-r635-xf49 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58084 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly. Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it. Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() Commit 2e4955167ec5 (&#34;firmware: qcom: scm: Fix __scm and waitq completion variable initialization&#34;) introduced a write barrier in probe function to store global &#39;__scm&#39; variable. We all known barriers are paired (see memory-barriers.txt: &#34;Note that write barriers should normally be paired with read or address-dependency barriers&#34;), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let&#39;s use that directly. Lack of this read barrier can result in fetching stale &#39;__scm&#39; variable value, NULL, and dereferencing it. Note that barrier in qcom_scm_is_available() satisfies here the control dependency.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58084 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0499 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0499