<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 18:37:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26775 — aoe: avoid potential deadlock at set_capacity</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26775</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;aoe: avoid potential deadlock at set_capacity&lt;/p&gt;
&lt;p&gt;Move set_capacity() outside of the section procected by (&amp;amp;d-&amp;gt;lock).
To avoid possible interrupt unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
        ----                    ----
[1] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);
                                local_irq_disable();
                            [2] lock(&amp;amp;d-&amp;gt;lock);
                            [3] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);
   &amp;lt;Interrupt&amp;gt;
[4]  lock(&amp;amp;d-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Where [1](&amp;amp;bdev-&amp;gt;bd_size_lock) hold by zram_add()-&amp;gt;set_capacity().
[2]lock(&amp;amp;d-&amp;gt;lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc()
is trying to acquire [3](&amp;amp;bdev-&amp;gt;bd_size_lock) at set_capacity() call.
In this situation an attempt to acquire [4]lock(&amp;amp;d-&amp;gt;lock) from
aoecmd_cfg_rsp() will lead to deadlock.&lt;/p&gt;
&lt;p&gt;So the simplest solution is breaking lock dependency
[2](&amp;amp;d-&amp;gt;lock) -&amp;gt; [3](&amp;amp;bdev-&amp;gt;bd_size_lock) by moving set_capacity()
outside.&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;aoe: avoid potential deadlock at set_capacity&lt;/p&gt;
&lt;p&gt;Move set_capacity() outside of the section procected by (&amp;amp;d-&amp;gt;lock).
To avoid possible interrupt unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
        ----                    ----
[1] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);
                                local_irq_disable();
                            [2] lock(&amp;amp;d-&amp;gt;lock);
                            [3] lock(&amp;amp;bdev-&amp;gt;bd_size_lock);
   &amp;lt;Interrupt&amp;gt;
[4]  lock(&amp;amp;d-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Where [1](&amp;amp;bdev-&amp;gt;bd_size_lock) hold by zram_add()-&amp;gt;set_capacity().
[2]lock(&amp;amp;d-&amp;gt;lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc()
is trying to acquire [3](&amp;amp;bdev-&amp;gt;bd_size_lock) at set_capacity() call.
In this situation an attempt to acquire [4]lock(&amp;amp;d-&amp;gt;lock) from
aoecmd_cfg_rsp() will lead to deadlock.&lt;/p&gt;
&lt;p&gt;So the simplest solution is breaking lock dependency
[2](&amp;amp;d-&amp;gt;lock) -&amp;gt; [3](&amp;amp;bdev-&amp;gt;bd_size_lock) by moving set_capacity()
outside.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26775</guid>
    </item>
  </channel>
</rss>
