<?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-19T17:57:46.373118+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/alsa-2025:11298</id>
    <title>ALSA-2025:11298 — Moderate: kernel security update</title>
    <updated>2026-11-19T17:57:46.388143+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: cifs: potential buffer overflow in handling symlinks (CVE-2022-49058)
  * kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)
  * kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)
  * kernel: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes (CVE-2025-21991)
  * kernel: net: atm: fix use after free in lec_send() (CVE-2025-22004)
  * kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)
  * kernel: ext4: ignore xattrs past end (CVE-2025-37738)
  * kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2025:11298"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0509</id>
    <title>certfr-2025-avi-0509 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-19T17:57:46.388263+00:00</updated>
    <content>certfr-2025-avi-0509</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0509"/>
  </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-19T17:57:46.388287+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-2022-49788</id>
    <title>UBUNTU-CVE-2022-49788</title>
    <updated>2026-11-19T17:57:46.388365+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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-oracle, Ubuntu:Pro:16.04:LTS: linux and 149 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() `struct vmci_event_qp` allocated by qp_notify_peer() contains padding, which may carry uninitialized data to the userspace, as observed by KMSAN:   BUG: KMSAN: kernel-infoleak in instrument_copy_to_user ./include/linux/instrumented.h:121    instrument_copy_to_user ./include/linux/instrumented.h:121    _copy_to_user+0x5f/0xb0 lib/usercopy.c:33    copy_to_user ./include/linux/uaccess.h:169    vmci_host_do_receive_datagram drivers/misc/vmw_vmci/vmci_host.c:431    vmci_host_unlocked_ioctl+0x33d/0x43d0 drivers/misc/vmw_vmci/vmci_host.c:925    vfs_ioctl fs/ioctl.c:51   ...   Uninit was stored to memory at:    kmemdup+0x74/0xb0 mm/util.c:131    dg_dispatch_as_host drivers/misc/vmw_vmci/vmci_datagram.c:271    vmci_datagram_dispatch+0x4f8/0xfc0 drivers/misc/vmw_vmci/vmci_datagram.c:339    qp_notify_peer+0x19a/0x290 drivers/misc/vmw_vmci/vmci_queue_pair.c:1479    qp_broker_attach drivers/misc/vmw_vmci/vmci_queue_pair.c:1662    qp_broker_alloc+0x2977/0x2f30 drivers/misc/vmw_vmci/vmci_queue_pair.c:1750    vmci_qp_broker_alloc+0x96/0xd0 drivers/misc/vmw_vmci/vmci_queue_pair.c:1940    vmci_host_do_alloc_queuepair drivers/misc/vmw_vmci/vmci_host.c:488    vmci_host_unlocked_ioctl+0x24fd/0x43d0 drivers/misc/vmw_vmci/vmci_host.c:927   ...   Local variable ev created at:    qp_notify_peer+0x54/0x290 drivers/misc/vmw_vmci/vmci_queue_pair.c:1456    qp_broker_attac…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2022-49788"/>
  </entry>
</feed>
