<?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 16:00:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46846 — spi: rockchip: Resolve unbalanced runtime PM / system PM handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46846</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: rockchip: Resolve unbalanced runtime PM / system PM handling&lt;/p&gt;
&lt;p&gt;Commit e882575efc77 (&amp;#34;spi: rockchip: Suspend and resume the bus during
NOIRQ_SYSTEM_SLEEP_PM ops&amp;#34;) stopped respecting runtime PM status and
simply disabled clocks unconditionally when suspending the system. This
causes problems when the device is already runtime suspended when we go
to sleep -- in which case we double-disable clocks and produce a
WARNing.&lt;/p&gt;
&lt;p&gt;Switch back to pm_runtime_force_{suspend,resume}(), because that still
seems like the right thing to do, and the aforementioned commit makes no
explanation why it stopped using it.&lt;/p&gt;
&lt;p&gt;Also, refactor some of the resume() error handling, because it&amp;#39;s not
actually a good idea to re-disable clocks on failure.&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: rockchip: Resolve unbalanced runtime PM / system PM handling&lt;/p&gt;
&lt;p&gt;Commit e882575efc77 (&amp;#34;spi: rockchip: Suspend and resume the bus during
NOIRQ_SYSTEM_SLEEP_PM ops&amp;#34;) stopped respecting runtime PM status and
simply disabled clocks unconditionally when suspending the system. This
causes problems when the device is already runtime suspended when we go
to sleep -- in which case we double-disable clocks and produce a
WARNing.&lt;/p&gt;
&lt;p&gt;Switch back to pm_runtime_force_{suspend,resume}(), because that still
seems like the right thing to do, and the aforementioned commit makes no
explanation why it stopped using it.&lt;/p&gt;
&lt;p&gt;Also, refactor some of the resume() error handling, because it&amp;#39;s not
actually a good idea to re-disable clocks on failure.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46846</guid>
    </item>
  </channel>
</rss>
