<?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>Fri, 02 Oct 2026 14:48:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56780 — quota: flush quota_release_work upon quota writeback</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56780</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;quota: flush quota_release_work upon quota writeback&lt;/p&gt;
&lt;p&gt;One of the paths quota writeback is called from is:&lt;/p&gt;
&lt;p&gt;freeze_super()
  sync_filesystem()
    ext4_sync_fs()
      dquot_writeback_dquots()&lt;/p&gt;
&lt;p&gt;Since we currently don&amp;#39;t always flush the quota_release_work queue in
this path, we can end up with the following race:&lt;/p&gt;
&lt;p&gt;1. dquot are added to releasing_dquots list during regular operations.
 2. FS Freeze starts, however, this does not flush the quota_release_work queue.
 3. Freeze completes.
 4. Kernel eventually tries to flush the workqueue while FS is frozen which
    hits a WARN_ON since transaction gets started during frozen state:&lt;/p&gt;
&lt;p&gt;ext4_journal_check_start+0x28/0x110 [ext4] (unreliable)
  __ext4_journal_start_sb+0x64/0x1c0 [ext4]
  ext4_release_dquot+0x90/0x1d0 [ext4]
  quota_release_workfn+0x43c/0x4d0&lt;/p&gt;
&lt;p&gt;Which is the following line:&lt;/p&gt;
&lt;p&gt;WARN_ON(sb-&amp;gt;s_writers.frozen == SB_FREEZE_COMPLETE);&lt;/p&gt;
&lt;p&gt;Which ultimately results in generic/390 failing due to dmesg
noise. This was detected on powerpc machine 15 cores.&lt;/p&gt;
&lt;p&gt;To avoid this, make sure to flush the workqueue during
dquot_writeback_dquots() so we dont have any pending workitems after
freeze.&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;quota: flush quota_release_work upon quota writeback&lt;/p&gt;
&lt;p&gt;One of the paths quota writeback is called from is:&lt;/p&gt;
&lt;p&gt;freeze_super()
  sync_filesystem()
    ext4_sync_fs()
      dquot_writeback_dquots()&lt;/p&gt;
&lt;p&gt;Since we currently don&amp;#39;t always flush the quota_release_work queue in
this path, we can end up with the following race:&lt;/p&gt;
&lt;p&gt;1. dquot are added to releasing_dquots list during regular operations.
 2. FS Freeze starts, however, this does not flush the quota_release_work queue.
 3. Freeze completes.
 4. Kernel eventually tries to flush the workqueue while FS is frozen which
    hits a WARN_ON since transaction gets started during frozen state:&lt;/p&gt;
&lt;p&gt;ext4_journal_check_start+0x28/0x110 [ext4] (unreliable)
  __ext4_journal_start_sb+0x64/0x1c0 [ext4]
  ext4_release_dquot+0x90/0x1d0 [ext4]
  quota_release_workfn+0x43c/0x4d0&lt;/p&gt;
&lt;p&gt;Which is the following line:&lt;/p&gt;
&lt;p&gt;WARN_ON(sb-&amp;gt;s_writers.frozen == SB_FREEZE_COMPLETE);&lt;/p&gt;
&lt;p&gt;Which ultimately results in generic/390 failing due to dmesg
noise. This was detected on powerpc machine 15 cores.&lt;/p&gt;
&lt;p&gt;To avoid this, make sure to flush the workqueue during
dquot_writeback_dquots() so we dont have any pending workitems after
freeze.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56780</guid>
    </item>
  </channel>
</rss>
