<?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:46:14 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37904</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37904</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-2025-37904</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0625 — De multiples vulnérabilités ont été découvertes dans Ubuntu Ubuntu. Certaines d'entre elles permettent à un attaquant d…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</link>
      <description>certfr-2025-avi-0625</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37904</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37904</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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix the inode leak in btrfs_iget() [BUG] There is a bug report that a syzbot reproducer can lead to the following busy inode at unmount time:   BTRFS info (device loop1): last unmount of filesystem 1680000e-3c1e-4c46-84b6-56bd3909af50   VFS: Busy inodes after unmount of loop1 (btrfs)   ------------[ cut here ]------------   kernel BUG at fs/super.c:650!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   CPU: 0 UID: 0 PID: 48168 Comm: syz-executor Not tainted 6.15.0-rc2-00471-g119009db2674 #2 PREEMPT(full)   Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014   RIP: 0010:generic_shutdown_super+0x2e9/0x390 fs/super.c:650   Call Trace:    &amp;lt;TASK&amp;gt;    kill_anon_super+0x3a/0x60 fs/super.c:1237    btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2099    deactivate_locked_super+0xbe/0x1a0 fs/super.c:473    deactivate_super fs/super.c:506 [inline]    deactivate_super+0xe2/0x100 fs/super.c:502    cleanup_mnt+0x21f/0x440 fs/namespace.c:1435    task_work_run+0x14d/0x240 kernel/task_work.c:227    resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]    exit_to_user_mode_loop kernel/entry/common.c:114 [inline]    exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]    __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]    syscall_exit_to_user_mode+0x269/0x290 kernel/entry/common.c:218    do_syscall_64+0xd4/0x250 arch/x86/entry/sysc…&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 77 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix the inode leak in btrfs_iget() [BUG] There is a bug report that a syzbot reproducer can lead to the following busy inode at unmount time:   BTRFS info (device loop1): last unmount of filesystem 1680000e-3c1e-4c46-84b6-56bd3909af50   VFS: Busy inodes after unmount of loop1 (btrfs)   ------------[ cut here ]------------   kernel BUG at fs/super.c:650!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   CPU: 0 UID: 0 PID: 48168 Comm: syz-executor Not tainted 6.15.0-rc2-00471-g119009db2674 #2 PREEMPT(full)   Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014   RIP: 0010:generic_shutdown_super+0x2e9/0x390 fs/super.c:650   Call Trace:    &amp;lt;TASK&amp;gt;    kill_anon_super+0x3a/0x60 fs/super.c:1237    btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2099    deactivate_locked_super+0xbe/0x1a0 fs/super.c:473    deactivate_super fs/super.c:506 [inline]    deactivate_super+0xe2/0x100 fs/super.c:502    cleanup_mnt+0x21f/0x440 fs/namespace.c:1435    task_work_run+0x14d/0x240 kernel/task_work.c:227    resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]    exit_to_user_mode_loop kernel/entry/common.c:114 [inline]    exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]    __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]    syscall_exit_to_user_mode+0x269/0x290 kernel/entry/common.c:218    do_syscall_64+0xd4/0x250 arch/x86/entry/sysc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37904</guid>
    </item>
  </channel>
</rss>
