<?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 03:47:35 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-48875</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-48875</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-2024-48875</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0254 — 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-2025-avi-0254</link>
      <description>certfr-2025-avi-0254</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0254</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-48875</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-48875</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: don&amp;#39;t take dev_replace rwsem on task already holding it Running fstests btrfs/011 with MKFS_OPTIONS=&amp;#34;-O rst&amp;#34; to force the usage of the RAID stripe-tree, we get the following splat from lockdep:  BTRFS info (device sdd): dev_replace from /dev/sdd (devid 1) to /dev/sdb started  ============================================  WARNING: possible recursive locking detected  6.11.0-rc3-btrfs-for-next #599 Not tainted  --------------------------------------------  btrfs/2326 is trying to acquire lock:  ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  but task is already holding lock:  ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  other info that might help us debug this:   Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;fs_info-&amp;gt;dev_replace.rwsem);    lock(&amp;amp;fs_info-&amp;gt;dev_replace.rwsem);   *** DEADLOCK ***   May be due to missing lock nesting notation  1 lock held by btrfs/2326:   #0: ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  stack backtrace:  CPU: 1 UID: 0 PID: 2326 Comm: btrfs Not tainted 6.11.0-rc3-btrfs-for-next #599  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0x5b/0x80   __lock_acquire+0x2798/0x69d0   ? __pfx___lock_acquire+0x10/0x10   ? __pfx___lock_acquire+0x10/0x10   lock_acquire+0x19d/0x4a0   ? b…&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: don&amp;#39;t take dev_replace rwsem on task already holding it Running fstests btrfs/011 with MKFS_OPTIONS=&amp;#34;-O rst&amp;#34; to force the usage of the RAID stripe-tree, we get the following splat from lockdep:  BTRFS info (device sdd): dev_replace from /dev/sdd (devid 1) to /dev/sdb started  ============================================  WARNING: possible recursive locking detected  6.11.0-rc3-btrfs-for-next #599 Not tainted  --------------------------------------------  btrfs/2326 is trying to acquire lock:  ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  but task is already holding lock:  ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  other info that might help us debug this:   Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;fs_info-&amp;gt;dev_replace.rwsem);    lock(&amp;amp;fs_info-&amp;gt;dev_replace.rwsem);   *** DEADLOCK ***   May be due to missing lock nesting notation  1 lock held by btrfs/2326:   #0: ffff88810f215c98 (&amp;amp;fs_info-&amp;gt;dev_replace.rwsem){++++}-{3:3}, at: btrfs_map_block+0x39f/0x2250  stack backtrace:  CPU: 1 UID: 0 PID: 2326 Comm: btrfs Not tainted 6.11.0-rc3-btrfs-for-next #599  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0x5b/0x80   __lock_acquire+0x2798/0x69d0   ? __pfx___lock_acquire+0x10/0x10   ? __pfx___lock_acquire+0x10/0x10   lock_acquire+0x19d/0x4a0   ? b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-48875</guid>
    </item>
  </channel>
</rss>
