<?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 14:44:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89495</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89495</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-89495</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89495</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89495</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: ocfs2: bound namelen in dlm_migrate_request_handler Patch series &amp;#34;ocfs2/dlm: bound peer-controlled lengths in the o2dlm&amp;#34;. The o2dlm receive handlers trust u8 length and count fields from the wire without bounding them, so a node in a DLM domain can corrupt or panic any other node with a malformed message.  Three defects:   - dlm_migrate_request_handler() passes migrate-&amp;gt;namelen unchecked to     dlm_init_mle(), which memcpy()s it into the 32-byte mname[] of an     o2dlm_mle slab object: a heap out-of-bounds write of up to ~215     attacker-controlled bytes.   - dlm_mig_lockres_handler() passes mres-&amp;gt;lockname_len unchecked to     dlm_init_lockres(), which memcpy()s it into the 32-byte o2dlm_lockname     slab object: a heap out-of-bounds write of up to ~223 bytes.   - the same handler trusts mres-&amp;gt;num_locks without checking that the     message is large enough to hold that many entries, so     dlm_process_recovery_data() walks mres-&amp;gt;ml[] past the kmalloc(data_len)     copy and trips a BUG_ON (an out-of-bounds read ending in a panic). The other o2dlm receive handlers already reject an oversized name; the migration and recovery handlers have omitted it since the DLM was added (see the Fixes tags).  Patch 1 bounds namelen; patch 2 validates lockname_len, num_locks, and the payload size.  Conforming recovery and migration traffic is unaffected. o2net authenticates peers only by the DLM domain key, so any node that…&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: ocfs2: bound namelen in dlm_migrate_request_handler Patch series &amp;#34;ocfs2/dlm: bound peer-controlled lengths in the o2dlm&amp;#34;. The o2dlm receive handlers trust u8 length and count fields from the wire without bounding them, so a node in a DLM domain can corrupt or panic any other node with a malformed message.  Three defects:   - dlm_migrate_request_handler() passes migrate-&amp;gt;namelen unchecked to     dlm_init_mle(), which memcpy()s it into the 32-byte mname[] of an     o2dlm_mle slab object: a heap out-of-bounds write of up to ~215     attacker-controlled bytes.   - dlm_mig_lockres_handler() passes mres-&amp;gt;lockname_len unchecked to     dlm_init_lockres(), which memcpy()s it into the 32-byte o2dlm_lockname     slab object: a heap out-of-bounds write of up to ~223 bytes.   - the same handler trusts mres-&amp;gt;num_locks without checking that the     message is large enough to hold that many entries, so     dlm_process_recovery_data() walks mres-&amp;gt;ml[] past the kmalloc(data_len)     copy and trips a BUG_ON (an out-of-bounds read ending in a panic). The other o2dlm receive handlers already reject an oversized name; the migration and recovery handlers have omitted it since the DLM was added (see the Fixes tags).  Patch 1 bounds namelen; patch 2 validates lockname_len, num_locks, and the payload size.  Conforming recovery and migration traffic is unaffected. o2net authenticates peers only by the DLM domain key, so any node that…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89495</guid>
    </item>
  </channel>
</rss>
