<?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 16:31:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89783</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89783</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-89783</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-89783</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89783</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: xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full The depth check in xfrm6_input_addr() is off by one:   if (1 + sp-&amp;gt;len == XFRM_MAX_DEPTH)           goto drop;   ...   sp-&amp;gt;xvec[sp-&amp;gt;len++] = x; xfrm_input() can leave sp-&amp;gt;len == XFRM_MAX_DEPTH, and the transport-mode receive path re-enters IPv6 input via xfrm_trans_reinject() with that secpath preserved. If the inner packet carries a destination-options HAO option or a type-2 routing header, xfrm6_input_addr() is called with sp-&amp;gt;len == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so sp-&amp;gt;xvec[sp-&amp;gt;len++] writes one slot past the 6-element xvec[]. The write stays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS flags it and panics under panic_on_warn. Use &amp;#34;sp-&amp;gt;len &amp;gt;= XFRM_MAX_DEPTH&amp;#34;, matching xfrm_input(). This also restores one chain level the old check rejected at sp-&amp;gt;len == 5.   UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10   index 6 is out of range for type &amp;#39;xfrm_state *[6]&amp;#39;&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: xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full The depth check in xfrm6_input_addr() is off by one:   if (1 + sp-&amp;gt;len == XFRM_MAX_DEPTH)           goto drop;   ...   sp-&amp;gt;xvec[sp-&amp;gt;len++] = x; xfrm_input() can leave sp-&amp;gt;len == XFRM_MAX_DEPTH, and the transport-mode receive path re-enters IPv6 input via xfrm_trans_reinject() with that secpath preserved. If the inner packet carries a destination-options HAO option or a type-2 routing header, xfrm6_input_addr() is called with sp-&amp;gt;len == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so sp-&amp;gt;xvec[sp-&amp;gt;len++] writes one slot past the 6-element xvec[]. The write stays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS flags it and panics under panic_on_warn. Use &amp;#34;sp-&amp;gt;len &amp;gt;= XFRM_MAX_DEPTH&amp;#34;, matching xfrm_input(). This also restores one chain level the old check rejected at sp-&amp;gt;len == 5.   UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10   index 6 is out of range for type &amp;#39;xfrm_state *[6]&amp;#39;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89783</guid>
    </item>
  </channel>
</rss>
