https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T16:44:15.374926+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-12206 bdu:2025-12206 2026-10-03T16:44:15.387839+00:00 bdu:2025-12206 https://cve.radiocsirt.org/vuln/bell-cve-2024-58084 BELL-CVE-2024-58084 2026-10-03T16:44:15.387881+00:00

Affected: Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer… 2026-10-03T16:44:15.387913+00:00 certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/euvd-2026-313976 EUVD-2026-313976 2026-10-03T16:44:15.387931+00:00 EUVD-2026-313976 https://cve.radiocsirt.org/vuln/fkie_cve-2024-58084 fkie_cve-2024-58084 2026-10-03T16:44:15.387942+00:00

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 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let's use that directly.

Lack of this read barrier can result in fetching stale '__scm' variable value, NULL, and dereferencing it.

Note that barrier in qcom_scm_is_available() satisfies here the control dependency.

 https://cve.radiocsirt.org/vuln/ghsa-q37x-r635-xf49 GHSA-q37x-r635-xf49 2026-10-03T16:44:15.388025+00:00

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 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let's use that directly.

Lack of this read barrier can result in fetching stale '__scm' variable value, NULL, and dereferencing it.

Note that barrier in qcom_scm_is_available() satisfies here the control dependency.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-58084 UBUNTU-CVE-2024-58084 2026-10-03T16:44:15.388072+00:00

Affected: 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

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 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let's use that directly. Lack of this read barrier can result in fetching stale '__scm' variable value, NULL, and dereferencing it. Note that barrier in qcom_scm_is_available() satisfies here the control dependency.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0499 WID-SEC-W-2025-0499 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T16:44:15.388334+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.