<?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:24:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64187</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64187</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-64187</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0930 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0930</link>
      <description>certfr-2026-avi-0930</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0930</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64187</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64187</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: fail recovery on a committed log item with no regions If the first op of a transaction is a bare transaction header (len == sizeof(struct xfs_trans_header)), xlog_recover_add_to_trans() adds an item but no region, leaving it on r_itemq with ri_cnt == 0 and ri_buf == NULL. The header can be split across op records, so later ops may still add regions; the item is only invalid if the transaction commits with none. The runtime commit path never emits such a transaction, so this only happens on a crafted log.  It came from an AI-assisted code audit of the recovery parser. xlog_recover_reorder_trans() calls ITEM_TYPE() on the item, which reads *(unsigned short *)item-&amp;gt;ri_buf[0].iov_base and faults on the NULL ri_buf.  Reject it there, before the commit handlers that also read ri_buf[0].  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  RIP: 0010:xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836)   xlog_recover_commit_trans (fs/xfs/xfs_log_recover.c:2043)   xlog_recover_process_data (fs/xfs/xfs_log_recover.c:2501)   xlog_do_recovery_pass (fs/xfs/xfs_log_recover.c:3244)   xlog_recover (fs/xfs/xfs_log_recover.c:3493)   xfs_log_mount (fs/xfs/xfs_log.c:618)   xfs_mountfs (fs/xfs/xfs_mount.c:1034)   xfs_fs_fill_super (fs/xfs/xfs_super.c:1938)   vfs_get_tree (fs/super.c:1695)   path_mount (fs/namespace.c:4161)   __x64_sys_mount (fs/namespace.c:4367)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: fail recovery on a committed log item with no regions If the first op of a transaction is a bare transaction header (len == sizeof(struct xfs_trans_header)), xlog_recover_add_to_trans() adds an item but no region, leaving it on r_itemq with ri_cnt == 0 and ri_buf == NULL. The header can be split across op records, so later ops may still add regions; the item is only invalid if the transaction commits with none. The runtime commit path never emits such a transaction, so this only happens on a crafted log.  It came from an AI-assisted code audit of the recovery parser. xlog_recover_reorder_trans() calls ITEM_TYPE() on the item, which reads *(unsigned short *)item-&amp;gt;ri_buf[0].iov_base and faults on the NULL ri_buf.  Reject it there, before the commit handlers that also read ri_buf[0].  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  RIP: 0010:xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836)   xlog_recover_commit_trans (fs/xfs/xfs_log_recover.c:2043)   xlog_recover_process_data (fs/xfs/xfs_log_recover.c:2501)   xlog_do_recovery_pass (fs/xfs/xfs_log_recover.c:3244)   xlog_recover (fs/xfs/xfs_log_recover.c:3493)   xfs_log_mount (fs/xfs/xfs_log.c:618)   xfs_mountfs (fs/xfs/xfs_mount.c:1034)   xfs_fs_fill_super (fs/xfs/xfs_super.c:1938)   vfs_get_tree (fs/super.c:1695)   path_mount (fs/namespace.c:4161)   __x64_sys_mount (fs/namespace.c:4367)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64187</guid>
    </item>
  </channel>
</rss>
