<?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 19:50:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57946 — virtio-blk: don't keep queue frozen during system suspend</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57946</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;virtio-blk: don&amp;#39;t keep queue frozen during system suspend&lt;/p&gt;
&lt;p&gt;Commit 4ce6e2db00de (&amp;#34;virtio-blk: Ensure no requests in virtqueues before
deleting vqs.&amp;#34;) replaces queue quiesce with queue freeze in virtio-blk&amp;#39;s
PM callbacks. And the motivation is to drain inflight IOs before suspending.&lt;/p&gt;
&lt;p&gt;block layer&amp;#39;s queue freeze looks very handy, but it is also easy to cause
deadlock, such as, any attempt to call into bio_queue_enter() may run into
deadlock if the queue is frozen in current context. There are all kinds
of -&amp;gt;suspend() called in suspend context, so keeping queue frozen in the
whole suspend context isn&amp;#39;t one good idea. And Marek reported lockdep
warning[1] caused by virtio-blk&amp;#39;s freeze queue in virtblk_freeze().&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/&lt;/p&gt;
&lt;p&gt;Given the motivation is to drain in-flight IOs, it can be done by calling
freeze &amp;amp; unfreeze, meantime restore to previous behavior by keeping queue
quiesced during suspend.&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;virtio-blk: don&amp;#39;t keep queue frozen during system suspend&lt;/p&gt;
&lt;p&gt;Commit 4ce6e2db00de (&amp;#34;virtio-blk: Ensure no requests in virtqueues before
deleting vqs.&amp;#34;) replaces queue quiesce with queue freeze in virtio-blk&amp;#39;s
PM callbacks. And the motivation is to drain inflight IOs before suspending.&lt;/p&gt;
&lt;p&gt;block layer&amp;#39;s queue freeze looks very handy, but it is also easy to cause
deadlock, such as, any attempt to call into bio_queue_enter() may run into
deadlock if the queue is frozen in current context. There are all kinds
of -&amp;gt;suspend() called in suspend context, so keeping queue frozen in the
whole suspend context isn&amp;#39;t one good idea. And Marek reported lockdep
warning[1] caused by virtio-blk&amp;#39;s freeze queue in virtblk_freeze().&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-block/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/&lt;/p&gt;
&lt;p&gt;Given the motivation is to drain in-flight IOs, it can be done by calling
freeze &amp;amp; unfreeze, meantime restore to previous behavior by keeping queue
quiesced during suspend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57946</guid>
    </item>
  </channel>
</rss>
