<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 09:17:45 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12219</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12219</link>
      <description>bdu:2025-12219</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12219</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-57985</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-57985</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-57985</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-346575</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346575</link>
      <description>EUVD-2026-346575</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346575</guid>
    </item>
    <item>
      <title>fkie_cve-2024-57985</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-57985</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures&lt;/p&gt;
&lt;p&gt;If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39;
variable assigned, because external users of this driver will assume the
probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;)
are initialized later in the probe, but users of it (__scm_smc_call())
rely on the &amp;#39;__scm&amp;#39; variable.&lt;/p&gt;
&lt;p&gt;This fixes theoretical NULL pointer exception, triggered via introducing
probe deferral in SCM driver with call trace:&lt;/p&gt;
&lt;p&gt;qcom_tzmem_alloc+0x70/0x1ac (P)
  qcom_tzmem_alloc+0x64/0x1ac (L)
  qcom_scm_assign_mem+0x78/0x194
  qcom_rmtfs_mem_probe+0x2d4/0x38c
  platform_probe+0x68/0xc8&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures&lt;/p&gt;
&lt;p&gt;If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39;
variable assigned, because external users of this driver will assume the
probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;)
are initialized later in the probe, but users of it (__scm_smc_call())
rely on the &amp;#39;__scm&amp;#39; variable.&lt;/p&gt;
&lt;p&gt;This fixes theoretical NULL pointer exception, triggered via introducing
probe deferral in SCM driver with call trace:&lt;/p&gt;
&lt;p&gt;qcom_tzmem_alloc+0x70/0x1ac (P)
  qcom_tzmem_alloc+0x64/0x1ac (L)
  qcom_scm_assign_mem+0x78/0x194
  qcom_rmtfs_mem_probe+0x2d4/0x38c
  platform_probe+0x68/0xc8&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-57985</guid>
    </item>
    <item>
      <title>GHSA-6grj-9h9x-cv46</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6grj-9h9x-cv46</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures&lt;/p&gt;
&lt;p&gt;If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39;
variable assigned, because external users of this driver will assume the
probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;)
are initialized later in the probe, but users of it (__scm_smc_call())
rely on the &amp;#39;__scm&amp;#39; variable.&lt;/p&gt;
&lt;p&gt;This fixes theoretical NULL pointer exception, triggered via introducing
probe deferral in SCM driver with call trace:&lt;/p&gt;
&lt;p&gt;qcom_tzmem_alloc+0x70/0x1ac (P)
  qcom_tzmem_alloc+0x64/0x1ac (L)
  qcom_scm_assign_mem+0x78/0x194
  qcom_rmtfs_mem_probe+0x2d4/0x38c
  platform_probe+0x68/0xc8&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures&lt;/p&gt;
&lt;p&gt;If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39;
variable assigned, because external users of this driver will assume the
probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;)
are initialized later in the probe, but users of it (__scm_smc_call())
rely on the &amp;#39;__scm&amp;#39; variable.&lt;/p&gt;
&lt;p&gt;This fixes theoretical NULL pointer exception, triggered via introducing
probe deferral in SCM driver with call trace:&lt;/p&gt;
&lt;p&gt;qcom_tzmem_alloc+0x70/0x1ac (P)
  qcom_tzmem_alloc+0x64/0x1ac (L)
  qcom_scm_assign_mem+0x78/0x194
  qcom_rmtfs_mem_probe+0x2d4/0x38c
  platform_probe+0x68/0xc8&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6grj-9h9x-cv46</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57985</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57985</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39; variable assigned, because external users of this driver will assume the probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;) are initialized later in the probe, but users of it (__scm_smc_call()) rely on the &amp;#39;__scm&amp;#39; variable. This fixes theoretical NULL pointer exception, triggered via introducing probe deferral in SCM driver with call trace:   qcom_tzmem_alloc+0x70/0x1ac (P)   qcom_tzmem_alloc+0x64/0x1ac (L)   qcom_scm_assign_mem+0x78/0x194   qcom_rmtfs_mem_probe+0x2d4/0x38c   platform_probe+0x68/0xc8&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Cleanup global &amp;#39;__scm&amp;#39; on probe failures If SCM driver fails the probe, it should not leave global &amp;#39;__scm&amp;#39; variable assigned, because external users of this driver will assume the probe finished successfully.  For example TZMEM parts (&amp;#39;__scm-&amp;gt;mempool&amp;#39;) are initialized later in the probe, but users of it (__scm_smc_call()) rely on the &amp;#39;__scm&amp;#39; variable. This fixes theoretical NULL pointer exception, triggered via introducing probe deferral in SCM driver with call trace:   qcom_tzmem_alloc+0x70/0x1ac (P)   qcom_tzmem_alloc+0x64/0x1ac (L)   qcom_scm_assign_mem+0x78/0x194   qcom_rmtfs_mem_probe+0x2d4/0x38c   platform_probe+0x68/0xc8&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57985</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0453 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453</guid>
    </item>
  </channel>
</rss>
