<?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 13:20:37 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74572</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74572</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-74572</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74572</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74572</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock between metadata writeback and transaction commit When writing out metadata extent buffers in a zoned filesystem, btree_writepages() holds fs_info-&amp;gt;zoned_meta_io_lock across the whole writeback loop, including the call to btrfs_check_meta_write_pointer() -&amp;gt; check_bg_is_active(). For the tree-log block group, check_bg_is_active() may fail to activate the zone and fall back to btrfs_zone_finish_one_bg() to free an active zone. That path waits for the running transaction to commit while still holding zoned_meta_io_lock, but the committer needs that same lock to write out the tree extents, so the two tasks deadlock:   Task A (kworker, metadata writeback)      Task B (fsstress, transaction commit)   ------------------------------------ -------------------------------------   wb_workfn()                               btrfs_commit_transaction(T)    btree_writepages() btrfs_write_and_wait_transaction()     btrfs_zoned_meta_io_lock()                btrfs_write_marked_extents()     btrfs_check_meta_write_pointer()           btree_writepages()      check_bg_is_active() [treelog_bg]          btrfs_zoned_meta_io_lock()       btrfs_zone_finish_one_bg()               &amp;lt;blocks on zoned_meta_io_lock,        btrfs_zone_finish()                      held by Task A&amp;gt;         do_zone_finish()          btrfs_inc_block_group_ro()           btrfs_wait_for_commit()            &amp;lt;blocks waiting for commit…&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock between metadata writeback and transaction commit When writing out metadata extent buffers in a zoned filesystem, btree_writepages() holds fs_info-&amp;gt;zoned_meta_io_lock across the whole writeback loop, including the call to btrfs_check_meta_write_pointer() -&amp;gt; check_bg_is_active(). For the tree-log block group, check_bg_is_active() may fail to activate the zone and fall back to btrfs_zone_finish_one_bg() to free an active zone. That path waits for the running transaction to commit while still holding zoned_meta_io_lock, but the committer needs that same lock to write out the tree extents, so the two tasks deadlock:   Task A (kworker, metadata writeback)      Task B (fsstress, transaction commit)   ------------------------------------ -------------------------------------   wb_workfn()                               btrfs_commit_transaction(T)    btree_writepages() btrfs_write_and_wait_transaction()     btrfs_zoned_meta_io_lock()                btrfs_write_marked_extents()     btrfs_check_meta_write_pointer()           btree_writepages()      check_bg_is_active() [treelog_bg]          btrfs_zoned_meta_io_lock()       btrfs_zone_finish_one_bg()               &amp;lt;blocks on zoned_meta_io_lock,        btrfs_zone_finish()                      held by Task A&amp;gt;         do_zone_finish()          btrfs_inc_block_group_ro()           btrfs_wait_for_commit()            &amp;lt;blocks waiting for commit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74572</guid>
    </item>
  </channel>
</rss>
