<?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 04:03:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64359</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64359</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, 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-64359</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64359</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64359</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers Syzbot reported a hung task in nilfs_transaction_begin() where multiple tasks performing chmod() on a nilfs2 mount blocked for over 143 seconds waiting to acquire ns_segctor_sem for read:   INFO: task syz.0.17:5918 blocked for more than 143 seconds.   Call Trace:    schedule+0x164/0x360    rwsem_down_read_slowpath+0x6d9/0x940    down_read+0x99/0x2e0    nilfs_transaction_begin+0x364/0x710 fs/nilfs2/segment.c:221    nilfs_setattr+0x124/0x2c0 fs/nilfs2/inode.c:921    notify_change+0xc1a/0xf40    chmod_common+0x273/0x4a0    do_fchmodat+0x12d/0x230 The writer holding ns_segctor_sem was a concurrent NILFS_IOCTL_CLEAN_SEGMENTS caller, stuck inside printk while emitting per-element warnings from nilfs_sufile_updatev():    __nilfs_msg+0x373/0x450 fs/nilfs2/super.c:78    nilfs_sufile_updatev+0x21c/0x6d0 fs/nilfs2/sufile.c:186    nilfs_sufile_freev fs/nilfs2/sufile.h:93 [inline]    nilfs_free_segments fs/nilfs2/segment.c:1140 [inline]    nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1261 [inline]    nilfs_segctor_do_construct+0x1f55/0x76c0    nilfs_clean_segments+0x3bd/0xa50    nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:922 [inline]    nilfs_ioctl+0x261f/0x2780 The root cause is that user-supplied segment numbers are not validated before nilfs_clean_segments() begins doing work; the range check on each segnum is performed deep inside the call ch…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers Syzbot reported a hung task in nilfs_transaction_begin() where multiple tasks performing chmod() on a nilfs2 mount blocked for over 143 seconds waiting to acquire ns_segctor_sem for read:   INFO: task syz.0.17:5918 blocked for more than 143 seconds.   Call Trace:    schedule+0x164/0x360    rwsem_down_read_slowpath+0x6d9/0x940    down_read+0x99/0x2e0    nilfs_transaction_begin+0x364/0x710 fs/nilfs2/segment.c:221    nilfs_setattr+0x124/0x2c0 fs/nilfs2/inode.c:921    notify_change+0xc1a/0xf40    chmod_common+0x273/0x4a0    do_fchmodat+0x12d/0x230 The writer holding ns_segctor_sem was a concurrent NILFS_IOCTL_CLEAN_SEGMENTS caller, stuck inside printk while emitting per-element warnings from nilfs_sufile_updatev():    __nilfs_msg+0x373/0x450 fs/nilfs2/super.c:78    nilfs_sufile_updatev+0x21c/0x6d0 fs/nilfs2/sufile.c:186    nilfs_sufile_freev fs/nilfs2/sufile.h:93 [inline]    nilfs_free_segments fs/nilfs2/segment.c:1140 [inline]    nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1261 [inline]    nilfs_segctor_do_construct+0x1f55/0x76c0    nilfs_clean_segments+0x3bd/0xa50    nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:922 [inline]    nilfs_ioctl+0x261f/0x2780 The root cause is that user-supplied segment numbers are not validated before nilfs_clean_segments() begins doing work; the range check on each segnum is performed deep inside the call ch…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64359</guid>
    </item>
  </channel>
</rss>
