<?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:25:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80994</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80994</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-80994</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>OESA-2026-4357 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-4357</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist&lt;/p&gt;
&lt;p&gt;Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.&lt;/p&gt;
&lt;p&gt;syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.&lt;/p&gt;
&lt;p&gt;Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;batman-adv: fix fragment reassembly length accounting&lt;/p&gt;
&lt;p&gt;batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.&lt;/p&gt;
&lt;p&gt;That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.&lt;/p&gt;
&lt;p&gt;Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.&lt;/p&gt;
&lt;p&gt;T…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-4357</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80994</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80994</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: net: openvswitch: fix flow mask use-after-free on flow deletion The commit in the Fixes tag below made so flow-&amp;gt;mask free is scheduled via RCU right after it is removed from the flow table.  The pointer stays in the flow structure and it can be accessible while in the same RCU critical section.  This is done to avoid requiring ovs_mutex for the ovs_flow_free(). However, while removing the flow during processing of CMD_DEL, we do not take RCU read lock before the removal, and ovs_flow_cmd_fill_info() uses the flow-&amp;gt;mask pointer afterwards.  The RCU read lock is taken, but it&amp;#39;s already late at that point.  The comment on that line acknowledges that the lock is cosmetic and doesn&amp;#39;t serve a real purpose. This leads to use-after-free if the RCU grace period passes between removal and the filling.  It is a short race window, but it is there and can lead to a real crash in case memory allocation for the info takes a bit longer:  BUG: KASAN: slab-use-after-free in __ovs_nla_put_key              net/openvswitch/flow_netlink.c:1996  BUG: KASAN: slab-use-after-free in ovs_nla_put_key+0x2463/0x2e30              net/openvswitch/flow_netlink.c:2250  Read of size 4 at addr ffff88801ee89970 by task ovs_flow_del_ec/9487  Call Trace:   &amp;lt;TASK&amp;gt;   __ovs_nla_put_key net/openvswitch/flow_netlink.c:1996   ovs_nla_put_key+0x2463/0x2e30 net/openvswitch/flow_netlink.c:2250   ovs_flow_cmd_fill_info+0x420/0x9c0 net/openvswitch/datapath.…&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: net: openvswitch: fix flow mask use-after-free on flow deletion The commit in the Fixes tag below made so flow-&amp;gt;mask free is scheduled via RCU right after it is removed from the flow table.  The pointer stays in the flow structure and it can be accessible while in the same RCU critical section.  This is done to avoid requiring ovs_mutex for the ovs_flow_free(). However, while removing the flow during processing of CMD_DEL, we do not take RCU read lock before the removal, and ovs_flow_cmd_fill_info() uses the flow-&amp;gt;mask pointer afterwards.  The RCU read lock is taken, but it&amp;#39;s already late at that point.  The comment on that line acknowledges that the lock is cosmetic and doesn&amp;#39;t serve a real purpose. This leads to use-after-free if the RCU grace period passes between removal and the filling.  It is a short race window, but it is there and can lead to a real crash in case memory allocation for the info takes a bit longer:  BUG: KASAN: slab-use-after-free in __ovs_nla_put_key              net/openvswitch/flow_netlink.c:1996  BUG: KASAN: slab-use-after-free in ovs_nla_put_key+0x2463/0x2e30              net/openvswitch/flow_netlink.c:2250  Read of size 4 at addr ffff88801ee89970 by task ovs_flow_del_ec/9487  Call Trace:   &amp;lt;TASK&amp;gt;   __ovs_nla_put_key net/openvswitch/flow_netlink.c:1996   ovs_nla_put_key+0x2463/0x2e30 net/openvswitch/flow_netlink.c:2250   ovs_flow_cmd_fill_info+0x420/0x9c0 net/openvswitch/datapath.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80994</guid>
    </item>
  </channel>
</rss>
