<?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 23:04:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53149 — ext4: avoid deadlock in fs reclaim with page writeback</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53149</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;ext4: avoid deadlock in fs reclaim with page writeback&lt;/p&gt;
&lt;p&gt;Ext4 has a filesystem wide lock protecting ext4_writepages() calls to
avoid races with switching of journalled data flag or inode format. This
lock can however cause a deadlock like:&lt;/p&gt;
&lt;p&gt;CPU0                            CPU1&lt;/p&gt;
&lt;p&gt;ext4_writepages()
  percpu_down_read(sbi-&amp;gt;s_writepages_rwsem);
                                ext4_change_inode_journal_flag()
                                  percpu_down_write(sbi-&amp;gt;s_writepages_rwsem);
                                    - blocks, all readers block from now on
  ext4_do_writepages()
    ext4_init_io_end()
      kmem_cache_zalloc(io_end_cachep, GFP_KERNEL)
        fs_reclaim frees dentry...
          dentry_unlink_inode()
            iput() - last ref =&amp;gt;
              iput_final() - inode dirty =&amp;gt;
                write_inode_now()...
                  ext4_writepages() tries to acquire sbi-&amp;gt;s_writepages_rwsem
                    and blocks forever&lt;/p&gt;
&lt;p&gt;Make sure we cannot recurse into filesystem reclaim from writeback code
to avoid the deadlock.&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;ext4: avoid deadlock in fs reclaim with page writeback&lt;/p&gt;
&lt;p&gt;Ext4 has a filesystem wide lock protecting ext4_writepages() calls to
avoid races with switching of journalled data flag or inode format. This
lock can however cause a deadlock like:&lt;/p&gt;
&lt;p&gt;CPU0                            CPU1&lt;/p&gt;
&lt;p&gt;ext4_writepages()
  percpu_down_read(sbi-&amp;gt;s_writepages_rwsem);
                                ext4_change_inode_journal_flag()
                                  percpu_down_write(sbi-&amp;gt;s_writepages_rwsem);
                                    - blocks, all readers block from now on
  ext4_do_writepages()
    ext4_init_io_end()
      kmem_cache_zalloc(io_end_cachep, GFP_KERNEL)
        fs_reclaim frees dentry...
          dentry_unlink_inode()
            iput() - last ref =&amp;gt;
              iput_final() - inode dirty =&amp;gt;
                write_inode_now()...
                  ext4_writepages() tries to acquire sbi-&amp;gt;s_writepages_rwsem
                    and blocks forever&lt;/p&gt;
&lt;p&gt;Make sure we cannot recurse into filesystem reclaim from writeback code
to avoid the deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53149</guid>
    </item>
  </channel>
</rss>
