<?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, 05 Oct 2026 10:57:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26806 — spi: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26806</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: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks&lt;/p&gt;
&lt;p&gt;The -&amp;gt;runtime_suspend() and -&amp;gt;runtime_resume() callbacks are not
expected to call spi_controller_suspend() and spi_controller_resume().
Remove calls to those in the cadence-qspi driver.&lt;/p&gt;
&lt;p&gt;Those helpers have two roles currently:
 - They stop/start the queue, including dealing with the kworker.
 - They toggle the SPI controller SPI_CONTROLLER_SUSPENDED flag. It
   requires acquiring ctlr-&amp;gt;bus_lock_mutex.&lt;/p&gt;
&lt;p&gt;Step one is irrelevant because cadence-qspi is not queued. Step two
however has two implications:
 - A deadlock occurs, because -&amp;gt;runtime_resume() is called in a context
   where the lock is already taken (in the -&amp;gt;exec_op() callback, where
   the usage count is incremented).
 - It would disallow all operations once the device is auto-suspended.&lt;/p&gt;
&lt;p&gt;Here is a brief call tree highlighting the mutex deadlock:&lt;/p&gt;
&lt;p&gt;spi_mem_exec_op()
        ...
        spi_mem_access_start()
                mutex_lock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)&lt;/p&gt;
&lt;p&gt;cqspi_exec_mem_op()
                pm_runtime_resume_and_get()
                        cqspi_resume()
                                spi_controller_resume()
                                        mutex_lock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)
                ...&lt;/p&gt;
&lt;p&gt;spi_mem_access_end()
                mutex_unlock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)
        ...&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: cadence-qspi: remove system-wide suspend helper calls from runtime PM hooks&lt;/p&gt;
&lt;p&gt;The -&amp;gt;runtime_suspend() and -&amp;gt;runtime_resume() callbacks are not
expected to call spi_controller_suspend() and spi_controller_resume().
Remove calls to those in the cadence-qspi driver.&lt;/p&gt;
&lt;p&gt;Those helpers have two roles currently:
 - They stop/start the queue, including dealing with the kworker.
 - They toggle the SPI controller SPI_CONTROLLER_SUSPENDED flag. It
   requires acquiring ctlr-&amp;gt;bus_lock_mutex.&lt;/p&gt;
&lt;p&gt;Step one is irrelevant because cadence-qspi is not queued. Step two
however has two implications:
 - A deadlock occurs, because -&amp;gt;runtime_resume() is called in a context
   where the lock is already taken (in the -&amp;gt;exec_op() callback, where
   the usage count is incremented).
 - It would disallow all operations once the device is auto-suspended.&lt;/p&gt;
&lt;p&gt;Here is a brief call tree highlighting the mutex deadlock:&lt;/p&gt;
&lt;p&gt;spi_mem_exec_op()
        ...
        spi_mem_access_start()
                mutex_lock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)&lt;/p&gt;
&lt;p&gt;cqspi_exec_mem_op()
                pm_runtime_resume_and_get()
                        cqspi_resume()
                                spi_controller_resume()
                                        mutex_lock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)
                ...&lt;/p&gt;
&lt;p&gt;spi_mem_access_end()
                mutex_unlock(&amp;amp;ctlr-&amp;gt;bus_lock_mutex)
        ...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26806</guid>
    </item>
  </channel>
</rss>
