<?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-21T03:12:37.756156+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-37752</id>
    <title>BELL-CVE-2025-37752</title>
    <updated>2026-11-21T03:12:37.764742+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-37752"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0463</id>
    <title>certfr-2025-avi-0463 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
    <updated>2026-11-21T03:12:37.764775+00:00</updated>
    <content>certfr-2025-avi-0463</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0463"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1569</id>
    <title>OESA-2025-1569 — kernel security update</title>
    <updated>2026-11-21T03:12:37.764787+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.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>gfs2: Check sb_bsize_shift after reading superblock</p>
<p>Fuzzers like to scribble over sb_bsize_shift but in reality it&amp;apos;s very
unlikely that this field would be corrupted on its own. Nevertheless it
should be checked to avoid the possibility of messy mount errors due to
bad calculations. It&amp;apos;s always a fixed value based on the block size so
we can just check that it&amp;apos;s the expected value.</p>
<p>Tested with:</p>
<p>mkfs.gfs2 -O -p lock_nolock /dev/vdb
    for i in 0 -1 64 65 32 33; do
        gfs2_edit -p sb field sb_bsize_shift $i /dev/vdb
        mount /dev/vdb /mnt/test &amp;amp;&amp;amp; umount /mnt/test
    done</p>
<p>Before this patch we get a withdraw after</p>
<p>[   76.413681] gfs2: fsid=loop0.0: fatal: invalid metadata block
[   76.413681]   bh = 19 (type: exp=5, found=4)
[   76.413681]   function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492</p>
<p>and with UBSAN configured we also get complaints like</p>
<p>[   76.373395] UBSAN: shift-out-of-bounds in fs/gfs2/ops_fstype.c:295:19
[   76.373815] shift exponent 4294967287 is too large for 64-bit type &amp;apos;long unsigned int&amp;apos;</p>
<p>After the patch, these complaints don&amp;apos;t appear, mount fails immediately
and we get an explanation in dmesg.(CVE-2022-49769)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram()</p>
<p>`s…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1569"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37752</id>
    <title>UBUNTU-CVE-2025-37752</title>
    <updated>2026-11-21T03:12:37.764838+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 111 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net_sched: sch_sfq: move the limit validation It is not sufficient to directly validate the limit on the data that the user passes as it can be updated based on how the other parameters are changed. Move the check at the end of the configuration update process to also catch scenarios where the limit is indirectly updated, for example with the following configurations: tc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 depth 1 tc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 divisor 1 This fixes the following syzkaller reported crash: ------------[ cut here ]------------ UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:203:6 index 65535 is out of range for type 'struct sfq_head[128]' CPU: 1 UID: 0 PID: 3037 Comm: syz.2.16 Not tainted 6.14.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 Call Trace:  &lt;TASK&gt;  __dump_stack lib/dump_stack.c:94 [inline]  dump_stack_lvl+0x201/0x300 lib/dump_stack.c:120  ubsan_epilogue lib/ubsan.c:231 [inline]  __ubsan_handle_out_of_bounds+0xf5/0x120 lib/ubsan.c:429  sfq_link net/sched/sch_sfq.c:203 [inline]  sfq_dec+0x53c/0x610 net/sched/sch_sfq.c:231  sfq_dequeue+0x34e/0x8c0 net/sched/sch_sfq.c:493  sfq_reset+0x17/0x60 net/sched/sch_sfq.c:518  qdisc_reset+0x12e/0x600 net/sched/sch_generic.c:1035  tbf_reset+0x41/0x110 net/sched/sch_tbf.c:339  qdisc_reset+0x12e/0x600 net/sched/sch_generic.c:1035  de…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37752"/>
  </entry>
</feed>
