<?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 00:17:23 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23018</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23018</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-23018</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23018</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23018</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 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before initializing extent tree in btrfs_read_locked_inode() In btrfs_read_locked_inode() we are calling btrfs_init_file_extent_tree() while holding a path with a read locked leaf from a subvolume tree, and btrfs_init_file_extent_tree() may do a GFP_KERNEL allocation, which can trigger reclaim. This can create a circular lock dependency which lockdep warns about with the following splat:    [6.1433] ======================================================    [6.1574] WARNING: possible circular locking dependency detected    [6.1583] 6.18.0+ #4 Tainted: G     U    [6.1591] ------------------------------------------------------    [6.1599] kswapd0/117 is trying to acquire lock:    [6.1606] ffff8d9b6333c5b8 (&amp;amp;delayed_node-&amp;gt;mutex){+.+.}-{3:3}, at: __btrfs_release_delayed_node.part.0+0x39/0x2f0    [6.1625]             but task is already holding lock:    [6.1633] ffffffffa4ab8ce0 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x195/0xc60    [6.1646]             which lock already depends on the new lock.    [6.1657]             the existing dependency chain (in reverse order) is:    [6.1667]             -&amp;gt; #2 (fs_reclaim){+.+.}-{0:0}:    [6.1677]        fs_reclaim_acquire+0x9d/0xd0    [6.1685]        __kmalloc_cache_noprof+0x59/0x750    [6.1694]        btrfs_init_file_extent_tree+0x90/0x100    [6.1702]        btrfs_read_locked_inode+0xc3/0x6b0    [6.1710]        btrfs_iget+0xbb/0xf0    [6.1716]…&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 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before initializing extent tree in btrfs_read_locked_inode() In btrfs_read_locked_inode() we are calling btrfs_init_file_extent_tree() while holding a path with a read locked leaf from a subvolume tree, and btrfs_init_file_extent_tree() may do a GFP_KERNEL allocation, which can trigger reclaim. This can create a circular lock dependency which lockdep warns about with the following splat:    [6.1433] ======================================================    [6.1574] WARNING: possible circular locking dependency detected    [6.1583] 6.18.0+ #4 Tainted: G     U    [6.1591] ------------------------------------------------------    [6.1599] kswapd0/117 is trying to acquire lock:    [6.1606] ffff8d9b6333c5b8 (&amp;amp;delayed_node-&amp;gt;mutex){+.+.}-{3:3}, at: __btrfs_release_delayed_node.part.0+0x39/0x2f0    [6.1625]             but task is already holding lock:    [6.1633] ffffffffa4ab8ce0 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0x195/0xc60    [6.1646]             which lock already depends on the new lock.    [6.1657]             the existing dependency chain (in reverse order) is:    [6.1667]             -&amp;gt; #2 (fs_reclaim){+.+.}-{0:0}:    [6.1677]        fs_reclaim_acquire+0x9d/0xd0    [6.1685]        __kmalloc_cache_noprof+0x59/0x750    [6.1694]        btrfs_init_file_extent_tree+0x90/0x100    [6.1702]        btrfs_read_locked_inode+0xc3/0x6b0    [6.1710]        btrfs_iget+0xbb/0xf0    [6.1716]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23018</guid>
    </item>
  </channel>
</rss>
