<?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-20T11:52:17.558834+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-2024-26863</id>
    <title>BELL-CVE-2024-26863</title>
    <updated>2026-11-20T11:52:17.576725+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-2024-26863"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</id>
    <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
    <updated>2026-11-20T11:52:17.576819+00:00</updated>
    <content>certfr-2024-avi-0381</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0381"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-1617</id>
    <title>OESA-2024-1617 — kernel security update</title>
    <updated>2026-11-20T11:52:17.576840+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

x86/kvm: Disable kvmclock on all CPUs on shutdown

Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.

Note, writing &amp;apos;0&amp;apos; to kvmclock MSR doesn&amp;apos;t clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don&amp;apos;t need to switch to some other clocksource.(CVE-2021-47110)

In the Linux kernel, the following vulnerability has been resolved:

i40e: Fix NULL ptr dereference on VSI filter sync

Remove the reason of null pointer dereference in sync VSI filters.
Added new I40E_VSI_RELEASING flag to signalize deleting and releasing
of VSI resources to sync this thread with sync filters subtask.
Without this patch it is possible to start update the VSI filter list
after VSI is removed, that&amp;apos;s causing a kernel oops.(CVE-2021-47184)

In the Linux kernel, the following vulnerability has been resolved:

erofs: fix pcluster use-after-free on UP platforms

During stress testing with CONFIG_SMP disabled, KASAN reports as below:

==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-1617"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26863</id>
    <title>UBUNTU-CVE-2024-26863</title>
    <updated>2026-11-20T11:52:17.577278+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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:Pro:16.04:LTS: linux-kvm and 171 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: hsr: Fix uninit-value access in hsr_get_node() KMSAN reported the following uninit-value access issue [1]: ===================================================== BUG: KMSAN: uninit-value in hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246  hsr_get_node+0xa2e/0xa40 net/hsr/hsr_framereg.c:246  fill_frame_info net/hsr/hsr_forward.c:577 [inline]  hsr_forward_skb+0xe12/0x30e0 net/hsr/hsr_forward.c:615  hsr_dev_xmit+0x1a1/0x270 net/hsr/hsr_device.c:223  __netdev_start_xmit include/linux/netdevice.h:4940 [inline]  netdev_start_xmit include/linux/netdevice.h:4954 [inline]  xmit_one net/core/dev.c:3548 [inline]  dev_hard_start_xmit+0x247/0xa10 net/core/dev.c:3564  __dev_queue_xmit+0x33b8/0x5130 net/core/dev.c:4349  dev_queue_xmit include/linux/netdevice.h:3134 [inline]  packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276  packet_snd net/packet/af_packet.c:3087 [inline]  packet_sendmsg+0x8b1d/0x9f30 net/packet/af_packet.c:3119  sock_sendmsg_nosec net/socket.c:730 [inline]  __sock_sendmsg net/socket.c:745 [inline]  __sys_sendto+0x735/0xa10 net/socket.c:2191  __do_sys_sendto net/socket.c:2203 [inline]  __se_sys_sendto net/socket.c:2199 [inline]  __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0x6d/0x140 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was created at:  slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768  slab_alloc_no…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26863"/>
  </entry>
</feed>
