<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 08:39:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56780</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56780</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-56780</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56780</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56780</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: flush quota_release_work upon quota writeback One of the paths quota writeback is called from is: freeze_super()   sync_filesystem()     ext4_sync_fs()       dquot_writeback_dquots() 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:  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:   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 Which is the following line:   WARN_ON(sb-&amp;gt;s_writers.frozen == SB_FREEZE_COMPLETE); Which ultimately results in generic/390 failing due to dmesg noise. This was detected on powerpc machine 15 cores. 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: flush quota_release_work upon quota writeback One of the paths quota writeback is called from is: freeze_super()   sync_filesystem()     ext4_sync_fs()       dquot_writeback_dquots() 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:  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:   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 Which is the following line:   WARN_ON(sb-&amp;gt;s_writers.frozen == SB_FREEZE_COMPLETE); Which ultimately results in generic/390 failing due to dmesg noise. This was detected on powerpc machine 15 cores. 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://127.0.0.1:10001/vuln/ubuntu-cve-2024-56780</guid>
    </item>
  </channel>
</rss>
