<?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 02:56:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31714</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31714</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-31714</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — 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-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31714</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31714</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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid memory leak in f2fs_rename() syzbot reported a f2fs bug as below: BUG: memory leak unreferenced object 0xffff888127f70830 (size 16):   comm &amp;#34;syz.0.23&amp;#34;, pid 6144, jiffies 4294943712   hex dump (first 16 bytes):     3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff  &amp;lt;.Wr[...n..3B9..   backtrace (crc 925f8a80):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4520 [inline]     slab_alloc_node mm/slub.c:4844 [inline]     __do_kmalloc_node mm/slub.c:5237 [inline]     __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250     kmalloc_noprof include/linux/slab.h:954 [inline]     fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364     f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143     f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961     f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308     vfs_rename+0x7ff/0x1250 fs/namei.c:6026     filename_renameat2+0x4f4/0x660 fs/namei.c:6144     __do_sys_renameat2 fs/namei.c:6173 [inline]     __se_sys_renameat2 fs/namei.c:6168 [inline]     __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]     do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94     entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in commit 40b2d55e0452 (&amp;#34;f2fs: fix to create selinux label during whiteout initialization&amp;#34;), we added a call to f2fs_setup_filename() without a matching call to f2fs…&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 153 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid memory leak in f2fs_rename() syzbot reported a f2fs bug as below: BUG: memory leak unreferenced object 0xffff888127f70830 (size 16):   comm &amp;#34;syz.0.23&amp;#34;, pid 6144, jiffies 4294943712   hex dump (first 16 bytes):     3c af 57 72 5b e6 8f ad 6e 8e fd 33 42 39 03 ff  &amp;lt;.Wr[...n..3B9..   backtrace (crc 925f8a80):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4520 [inline]     slab_alloc_node mm/slub.c:4844 [inline]     __do_kmalloc_node mm/slub.c:5237 [inline]     __kmalloc_noprof+0x3bd/0x560 mm/slub.c:5250     kmalloc_noprof include/linux/slab.h:954 [inline]     fscrypt_setup_filename+0x15e/0x3b0 fs/crypto/fname.c:364     f2fs_setup_filename+0x52/0xb0 fs/f2fs/dir.c:143     f2fs_rename+0x159/0xca0 fs/f2fs/namei.c:961     f2fs_rename2+0xd5/0xf20 fs/f2fs/namei.c:1308     vfs_rename+0x7ff/0x1250 fs/namei.c:6026     filename_renameat2+0x4f4/0x660 fs/namei.c:6144     __do_sys_renameat2 fs/namei.c:6173 [inline]     __se_sys_renameat2 fs/namei.c:6168 [inline]     __x64_sys_renameat2+0x59/0x80 fs/namei.c:6168     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]     do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94     entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in commit 40b2d55e0452 (&amp;#34;f2fs: fix to create selinux label during whiteout initialization&amp;#34;), we added a call to f2fs_setup_filename() without a matching call to f2fs…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31714</guid>
    </item>
  </channel>
</rss>
