<?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 07:21:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21807 — block: fix queue freeze vs limits lock order in sysfs store methods</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21807</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;block: fix queue freeze vs limits lock order in sysfs store methods&lt;/p&gt;
&lt;p&gt;queue_attr_store() always freezes a device queue before calling the
attribute store operation. For attributes that control queue limits, the
store operation will also lock the queue limits with a call to
queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may
need to issue commands to a device to obtain limit values from the
hardware with the queue limits locked. This creates a potential ABBA
deadlock situation if a user attempts to modify a limit (thus freezing
the device queue) while the device driver starts a revalidation of the
device queue limits.&lt;/p&gt;
&lt;p&gt;Avoid such deadlock by not freezing the queue before calling the
-&amp;gt;store_limit() method in struct queue_sysfs_entry and instead use the
queue_limits_commit_update_frozen helper to freeze the queue after taking
the limits lock.&lt;/p&gt;
&lt;p&gt;This also removes taking the sysfs lock for the store_limit method as
it doesn&amp;#39;t protect anything here, but creates even more nesting.
Hopefully it will go away from the actual sysfs methods entirely soon.&lt;/p&gt;
&lt;p&gt;(commit log adapted from a similar patch from  Damien Le Moal)&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;block: fix queue freeze vs limits lock order in sysfs store methods&lt;/p&gt;
&lt;p&gt;queue_attr_store() always freezes a device queue before calling the
attribute store operation. For attributes that control queue limits, the
store operation will also lock the queue limits with a call to
queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may
need to issue commands to a device to obtain limit values from the
hardware with the queue limits locked. This creates a potential ABBA
deadlock situation if a user attempts to modify a limit (thus freezing
the device queue) while the device driver starts a revalidation of the
device queue limits.&lt;/p&gt;
&lt;p&gt;Avoid such deadlock by not freezing the queue before calling the
-&amp;gt;store_limit() method in struct queue_sysfs_entry and instead use the
queue_limits_commit_update_frozen helper to freeze the queue after taking
the limits lock.&lt;/p&gt;
&lt;p&gt;This also removes taking the sysfs lock for the store_limit method as
it doesn&amp;#39;t protect anything here, but creates even more nesting.
Hopefully it will go away from the actual sysfs methods entirely soon.&lt;/p&gt;
&lt;p&gt;(commit log adapted from a similar patch from  Damien Le Moal)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21807</guid>
    </item>
  </channel>
</rss>
