<?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>Mon, 28 Sep 2026 23:40:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53758 — spi: atmel-quadspi: Free resources even if runtime resume failed in .remove()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53758</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: atmel-quadspi: Free resources even if runtime resume failed in .remove()&lt;/p&gt;
&lt;p&gt;An early error exit in atmel_qspi_remove() doesn&amp;#39;t prevent the device
unbind. So this results in an spi controller with an unbound parent
and unmapped register space (because devm_ioremap_resource() is undone).
So using the remaining spi controller probably results in an oops.&lt;/p&gt;
&lt;p&gt;Instead unregister the controller unconditionally and only skip hardware
access and clk disable.&lt;/p&gt;
&lt;p&gt;Also add a warning about resume failing and return zero unconditionally.
The latter has the only effect to suppress a less helpful error message by
the spi core.&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: atmel-quadspi: Free resources even if runtime resume failed in .remove()&lt;/p&gt;
&lt;p&gt;An early error exit in atmel_qspi_remove() doesn&amp;#39;t prevent the device
unbind. So this results in an spi controller with an unbound parent
and unmapped register space (because devm_ioremap_resource() is undone).
So using the remaining spi controller probably results in an oops.&lt;/p&gt;
&lt;p&gt;Instead unregister the controller unconditionally and only skip hardware
access and clk disable.&lt;/p&gt;
&lt;p&gt;Also add a warning about resume failing and return zero unconditionally.
The latter has the only effect to suppress a less helpful error message by
the spi core.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53758</guid>
    </item>
  </channel>
</rss>
