<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T10:57:45.485159+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-53041</id>
    <title>BELL-CVE-2026-53041</title>
    <updated>2026-11-21T10:57:45.502309+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-53041"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</id>
    <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
    <updated>2026-11-21T10:57:45.502355+00:00</updated>
    <content>certfr-2026-avi-0862</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0862"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-4357</id>
    <title>OESA-2026-4357 — kernel security update</title>
    <updated>2026-11-21T10:57:45.502373+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist</p>
<p>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.</p>
<p>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.</p>
<p>Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>batman-adv: fix fragment reassembly length accounting</p>
<p>batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.</p>
<p>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.</p>
<p>Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.</p>
<p>T…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-4357"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53041</id>
    <title>UBUNTU-CVE-2026-53041</title>
    <updated>2026-11-21T10:57:45.502731+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 255 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix listxattr handling when the buffer is full [BUG] If an OCFS2 inode has both inline and block-based xattrs, listxattr() can return a size larger than the caller's buffer when the inline names consume that buffer exactly. kernel BUG at mm/usercopy.c:102! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:usercopy_abort+0xb7/0xd0 mm/usercopy.c:102 Call Trace:  __check_heap_object+0xe3/0x120 mm/slub.c:8243  check_heap_object mm/usercopy.c:196 [inline]  __check_object_size mm/usercopy.c:250 [inline]  __check_object_size+0x5c5/0x780 mm/usercopy.c:215  check_object_size include/linux/ucopysize.h:22 [inline]  check_copy_size include/linux/ucopysize.h:59 [inline]  copy_to_user include/linux/uaccess.h:219 [inline]  listxattr+0xb0/0x170 fs/xattr.c:926  filename_listxattr fs/xattr.c:958 [inline]  path_listxattrat+0x137/0x320 fs/xattr.c:988  __do_sys_listxattr fs/xattr.c:1001 [inline]  __se_sys_listxattr fs/xattr.c:998 [inline]  __x64_sys_listxattr+0x7f/0xd0 fs/xattr.c:998  ... [CAUSE] Commit 936b8834366e ("ocfs2: Refactor xattr list and remove ocfs2_xattr_handler().") replaced the old per-handler list accounting with ocfs2_xattr_list_entry(), but it kept using size == 0 to detect probe mode. That assumption stops being true once ocfs2_listxattr() finishes the inline-xattr pass. If the inline names fill the caller buffer exactly, the block-xattr pass runs with a non-NULL buffer and a remaining size of z…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53041"/>
  </entry>
</feed>
