<?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-19T19:18:49.645891+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-2023-52621</id>
    <title>BELL-CVE-2023-52621</title>
    <updated>2026-11-19T19:18:49.658590+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-2023-52621"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-0329</id>
    <title>certfr-2024-avi-0329 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
    <updated>2026-11-19T19:18:49.658663+00:00</updated>
    <content>certfr-2024-avi-0329</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-0329"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-1647</id>
    <title>OESA-2024-1647 — kernel security update</title>
    <updated>2026-11-19T19:18:49.658684+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):

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

i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()

memcpy() is called in a loop while &amp;apos;operation-&amp;gt;length&amp;apos; upper bound
is not checked and &amp;apos;data_idx&amp;apos; also increments.(CVE-2022-48632)

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

mm/slub: fix to return errno if kmalloc() fails

In create_unique_id(), kmalloc(, GFP_KERNEL) can fail due to
out-of-memory, if it fails, return errno correctly rather than
triggering panic via BUG_ON();

kernel BUG at mm/slub.c:5893!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP

Call trace:
 sysfs_slab_add+0x258/0x260 mm/slub.c:5973
 __kmem_cache_create+0x60/0x118 mm/slub.c:4899
 create_cache mm/slab_common.c:229 [inline]
 kmem_cache_create_usercopy+0x19c/0x31c mm/slab_common.c:335
 kmem_cache_create+0x1c/0x28 mm/slab_common.c:390
 f2fs_kmem_cache_create fs/f2fs/f2fs.h:2766 [inline]
 f2fs_init_xattr_caches+0x78/0xb4 fs/f2fs/xattr.c:808
 f2fs_fill_super+0x1050/0x1e0c fs/f2fs/super.c:4149
 mount_bdev+0x1b8/0x210 fs/super.c:1400
 f2fs_mount+0x44/0x58 fs/f2fs/super.c:4512
 legacy_get_tree+0x30/0x74 fs/fs_context.c:610
 vfs_get_tree+0x40/0x140 fs/super.c:1530
 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
 path_mount+0x358/0x914 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-1647"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52621</id>
    <title>UBUNTU-CVE-2023-52621</title>
    <updated>2026-11-19T19:18:49.659162+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 104 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers These three bpf_map_{lookup,update,delete}_elem() helpers are also available for sleepable bpf program, so add the corresponding lock assertion for sleepable bpf program, otherwise the following warning will be reported when a sleepable bpf program manipulates bpf map under interpreter mode (aka bpf_jit_enable=0):   WARNING: CPU: 3 PID: 4985 at kernel/bpf/helpers.c:40 ......   CPU: 3 PID: 4985 Comm: test_progs Not tainted 6.6.0+ #2   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ......   RIP: 0010:bpf_map_lookup_elem+0x54/0x60   ......   Call Trace:    &lt;TASK&gt;    ? __warn+0xa5/0x240    ? bpf_map_lookup_elem+0x54/0x60    ? report_bug+0x1ba/0x1f0    ? handle_bug+0x40/0x80    ? exc_invalid_op+0x18/0x50    ? asm_exc_invalid_op+0x1b/0x20    ? __pfx_bpf_map_lookup_elem+0x10/0x10    ? rcu_lockdep_current_cpu_online+0x65/0xb0    ? rcu_is_watching+0x23/0x50    ? bpf_map_lookup_elem+0x54/0x60    ? __pfx_bpf_map_lookup_elem+0x10/0x10    ___bpf_prog_run+0x513/0x3b70    __bpf_prog_run32+0x9d/0xd0    ? __bpf_prog_enter_sleepable_recur+0xad/0x120    ? __bpf_prog_enter_sleepable_recur+0x3e/0x120    bpf_trampoline_6442580665+0x4d/0x1000    __x64_sys_getpgid+0x5/0x30    ? do_syscall_64+0x36/0xb0    entry_SYSCALL_64_after_hwframe+0x6e/0x76    &lt;/TASK&gt;</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2023-52621"/>
  </entry>
</feed>
