<?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>Sat, 03 Oct 2026 06:20:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04111</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04111</link>
      <description>bdu:2026-04111</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04111</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53658</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53658</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1009 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1009</link>
      <description>certfr-2025-avi-1009</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1009</guid>
    </item>
    <item>
      <title>EUVD-2026-312188</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312188</link>
      <description>EUVD-2026-312188</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312188</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53658</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53658</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spi: bcm-qspi: return error if neither hif_mspi nor mspi is available&lt;/p&gt;
&lt;p&gt;If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will
just early exit in probe but still return success. Apart from not doing
anything meaningful, this would then also lead to a null pointer access
on removal, as platform_get_drvdata() would return NULL, which it would
then try to dereference when trying to unregister the spi master.&lt;/p&gt;
&lt;p&gt;Fix this by unconditionally calling devm_ioremap_resource(), as it can
handle a NULL res and will then return a viable ERR_PTR() if we get one.&lt;/p&gt;
&lt;p&gt;The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then
ret was returned, but since ret was still initialized to 0 at this place
this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix
use-after-free on unbind&amp;#34;). The issue was not introduced by this commit,
only made more obvious.&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;spi: bcm-qspi: return error if neither hif_mspi nor mspi is available&lt;/p&gt;
&lt;p&gt;If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will
just early exit in probe but still return success. Apart from not doing
anything meaningful, this would then also lead to a null pointer access
on removal, as platform_get_drvdata() would return NULL, which it would
then try to dereference when trying to unregister the spi master.&lt;/p&gt;
&lt;p&gt;Fix this by unconditionally calling devm_ioremap_resource(), as it can
handle a NULL res and will then return a viable ERR_PTR() if we get one.&lt;/p&gt;
&lt;p&gt;The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then
ret was returned, but since ret was still initialized to 0 at this place
this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix
use-after-free on unbind&amp;#34;). The issue was not introduced by this commit,
only made more obvious.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53658</guid>
    </item>
    <item>
      <title>GHSA-f5pr-pcc8-pgcp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f5pr-pcc8-pgcp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spi: bcm-qspi: return error if neither hif_mspi nor mspi is available&lt;/p&gt;
&lt;p&gt;If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will
just early exit in probe but still return success. Apart from not doing
anything meaningful, this would then also lead to a null pointer access
on removal, as platform_get_drvdata() would return NULL, which it would
then try to dereference when trying to unregister the spi master.&lt;/p&gt;
&lt;p&gt;Fix this by unconditionally calling devm_ioremap_resource(), as it can
handle a NULL res and will then return a viable ERR_PTR() if we get one.&lt;/p&gt;
&lt;p&gt;The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then
ret was returned, but since ret was still initialized to 0 at this place
this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix
use-after-free on unbind&amp;#34;). The issue was not introduced by this commit,
only made more obvious.&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;spi: bcm-qspi: return error if neither hif_mspi nor mspi is available&lt;/p&gt;
&lt;p&gt;If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will
just early exit in probe but still return success. Apart from not doing
anything meaningful, this would then also lead to a null pointer access
on removal, as platform_get_drvdata() would return NULL, which it would
then try to dereference when trying to unregister the spi master.&lt;/p&gt;
&lt;p&gt;Fix this by unconditionally calling devm_ioremap_resource(), as it can
handle a NULL res and will then return a viable ERR_PTR() if we get one.&lt;/p&gt;
&lt;p&gt;The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then
ret was returned, but since ret was still initialized to 0 at this place
this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix
use-after-free on unbind&amp;#34;). The issue was not introduced by this commit,
only made more obvious.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f5pr-pcc8-pgcp</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21040-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21040-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:21040-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53658</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will just early exit in probe but still return success. Apart from not doing anything meaningful, this would then also lead to a null pointer access on removal, as platform_get_drvdata() would return NULL, which it would then try to dereference when trying to unregister the spi master. Fix this by unconditionally calling devm_ioremap_resource(), as it can handle a NULL res and will then return a viable ERR_PTR() if we get one. The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then ret was returned, but since ret was still initialized to 0 at this place this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix use-after-free on unbind&amp;#34;). The issue was not introduced by this commit, only made more obvious.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a &amp;#34;hif_mspi&amp;#34; nor &amp;#34;mspi&amp;#34; resource is present, the driver will just early exit in probe but still return success. Apart from not doing anything meaningful, this would then also lead to a null pointer access on removal, as platform_get_drvdata() would return NULL, which it would then try to dereference when trying to unregister the spi master. Fix this by unconditionally calling devm_ioremap_resource(), as it can handle a NULL res and will then return a viable ERR_PTR() if we get one. The &amp;#34;return 0;&amp;#34; was previously a &amp;#34;goto qspi_resource_err;&amp;#34; where then ret was returned, but since ret was still initialized to 0 at this place this was a valid conversion in 63c5395bb7a9 (&amp;#34;spi: bcm-qspi: Fix use-after-free on unbind&amp;#34;). The issue was not introduced by this commit, only made more obvious.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53658</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</guid>
    </item>
  </channel>
</rss>
