<?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, 06 Oct 2026 14:10:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49406 — block: Fix potential deadlock in blk_ia_range_sysfs_show()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49406</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 potential deadlock in blk_ia_range_sysfs_show()&lt;/p&gt;
&lt;p&gt;When being read, a sysfs attribute is already protected against removal
with the kobject node active reference counter. As a result, in
blk_ia_range_sysfs_show(), there is no need to take the queue sysfs
lock when reading the value of a range attribute. Using the queue sysfs
lock in this function creates a potential deadlock situation with the
disk removal, something that a lockdep signals with a splat when the
device is removed:&lt;/p&gt;
&lt;p&gt;[  760.703551]  Possible unsafe locking scenario:
[  760.703551]
[  760.703554]        CPU0                    CPU1
[  760.703556]        ----                    ----
[  760.703558]   lock(&amp;amp;q-&amp;gt;sysfs_lock);
[  760.703565]                                lock(kn-&amp;gt;active#385);
[  760.703573]                                lock(&amp;amp;q-&amp;gt;sysfs_lock);
[  760.703579]   lock(kn-&amp;gt;active#385);
[  760.703587]
[  760.703587]  *** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Solve this by removing the mutex_lock()/mutex_unlock() calls from
blk_ia_range_sysfs_show().&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 potential deadlock in blk_ia_range_sysfs_show()&lt;/p&gt;
&lt;p&gt;When being read, a sysfs attribute is already protected against removal
with the kobject node active reference counter. As a result, in
blk_ia_range_sysfs_show(), there is no need to take the queue sysfs
lock when reading the value of a range attribute. Using the queue sysfs
lock in this function creates a potential deadlock situation with the
disk removal, something that a lockdep signals with a splat when the
device is removed:&lt;/p&gt;
&lt;p&gt;[  760.703551]  Possible unsafe locking scenario:
[  760.703551]
[  760.703554]        CPU0                    CPU1
[  760.703556]        ----                    ----
[  760.703558]   lock(&amp;amp;q-&amp;gt;sysfs_lock);
[  760.703565]                                lock(kn-&amp;gt;active#385);
[  760.703573]                                lock(&amp;amp;q-&amp;gt;sysfs_lock);
[  760.703579]   lock(kn-&amp;gt;active#385);
[  760.703587]
[  760.703587]  *** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Solve this by removing the mutex_lock()/mutex_unlock() calls from
blk_ia_range_sysfs_show().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49406</guid>
    </item>
  </channel>
</rss>
