<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 05:39:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53658 — spi: bcm-qspi: return error if neither hif_mspi nor mspi is available</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2023-53658</guid>
    </item>
  </channel>
</rss>
