<?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-20T22:29:27.970656+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-2025-38100</id>
    <title>BELL-CVE-2025-38100</title>
    <updated>2026-11-20T22:29:27.987515+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-2025-38100"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</id>
    <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-20T22:29:27.987609+00:00</updated>
    <content>certfr-2025-avi-0698</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0698"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-2765</id>
    <title>OESA-2025-2765 — kernel security update</title>
    <updated>2026-11-20T22:29:27.987632+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.(CVE-2024-36357)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fs/ntfs3: Prevent integer overflow in hdr_first_de()</p>
<p>The &amp;quot;de_off&amp;quot; and &amp;quot;used&amp;quot; variables come from the disk so they both need to
check.  The problem is that on 32bit systems if they&amp;apos;re both greater than
UINT_MAX - 16 then the check does work as intended because of an integer
overflow.(CVE-2025-22080)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: fix off-by-one error in do_split</p>
<p>Syzkaller detected a use-after-free issue in ext4_insert_dentry that was
caused by out-of-bounds access due to incorrect splitting in do_split.</p>
<p>BUG: KASAN: use-after-free in ext4_insert_dentry+0x36a/0x6d0 fs/ext4/namei.c:2109
Write of size 251 at addr ffff888074572f14 by task syz-executor335/5847</p>
<p>CPU: 0 UID: 0 PID: 5847 Comm: syz-executor335 Not tainted 6.12.0-rc6-syzkaller-00318-ga9cda7c0ffed #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:377 [inline]
 print_report+0x169/0x550 mm/k…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-2765"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38100</id>
    <title>UBUNTU-CVE-2025-38100</title>
    <updated>2026-11-20T22:29:27.987967+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 159 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem:   1) io_bitmap_exit() should not invoke task_update_io_bitmap() when      the task, which is cleaned up, is not the current task. That's a      clear indicator for a cleanup after a failed fork().   2) A task should not have TIF_IO_BITMAP set and neither a bitmap      installed nor IOPL emulation level 3 activated.      This happens when a kernel thread is created in the context of      a user space thread, which has TIF_IO_BITMAP set as the thread      flags are copied and the IO bitmap pointer is cleared.      Other than in the failed fork() case this has no impact because      kernel threads including IO workers never return to user space and      therefore never invoke tss_update_io_bitmap(). Cure this by adding the missing cleanups and checks:   1) Prevent io_bitmap_exit() to invoke task_update_io_bitmap() if      the to be cleaned up task is not the current task…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38100"/>
  </entry>
</feed>
