<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T14:34:24.185425+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</id>
    <title>certfr-2026-avi-0108 — 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-10-03T14:34:24.540266+00:00</updated>
    <content>certfr-2026-avi-0108</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-311408</id>
    <title>EUVD-2026-311408</title>
    <updated>2026-10-03T14:34:24.540324+00:00</updated>
    <content>EUVD-2026-311408</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-311408"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50738</id>
    <title>fkie_cve-2022-50738</title>
    <updated>2026-10-03T14:34:24.540341+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>vhost-vdpa: fix an iotlb memory leak</p>
<p>Before commit 3d5698793897 ("vhost-vdpa: introduce asid based IOTLB")
we called vhost_vdpa_iotlb_unmap(v, iotlb, 0ULL, 0ULL - 1) during
release to free all the resources allocated when processing user IOTLB
messages through vhost_vdpa_process_iotlb_update().
That commit changed the handling of IOTLB a bit, and we accidentally
removed some code called during the release.</p>
<p>We partially fixed this with commit 037d4305569a ("vhost-vdpa: call
vhost_vdpa_cleanup during the release") but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:</p>
<p>unreferenced object 0xffff888007fbaa30 (size 16):
    comm "blkio-bench", pid 914, jiffies 4294993521 (age 885.500s)
    hex dump (first 16 bytes):
      40 73 41 07 80 88 ff ff 00 00 00 00 00 00 00 00  @sA.............
    backtrace:
      [&lt;0000000087736d2a&gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&lt;0000000060740f50&gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&lt;0000000083e8e205&gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&lt;000000008f2f414a&gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&lt;00000000de1cd4a0&gt;] vfs_write+0x216/0x4b0
      [&lt;00000000a2850200&gt;] ksys_write+0x71/0xf0
      [&lt;00000000de8e720b&gt;] __x64_sys_write+0x19/0x20
      [&lt;0000000018b12cbb&gt;] do_syscall_64+0x3f/0x90
      [&lt;00000000986ec465&gt;] entry_SYSCALL_64_after_hw…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-50738"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hfjw-rcpx-5rv6</id>
    <title>GHSA-hfjw-rcpx-5rv6</title>
    <updated>2026-10-03T14:34:24.540407+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>vhost-vdpa: fix an iotlb memory leak</p>
<p>Before commit 3d5698793897 ("vhost-vdpa: introduce asid based IOTLB")
we called vhost_vdpa_iotlb_unmap(v, iotlb, 0ULL, 0ULL - 1) during
release to free all the resources allocated when processing user IOTLB
messages through vhost_vdpa_process_iotlb_update().
That commit changed the handling of IOTLB a bit, and we accidentally
removed some code called during the release.</p>
<p>We partially fixed this with commit 037d4305569a ("vhost-vdpa: call
vhost_vdpa_cleanup during the release") but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:</p>
<p>unreferenced object 0xffff888007fbaa30 (size 16):
    comm "blkio-bench", pid 914, jiffies 4294993521 (age 885.500s)
    hex dump (first 16 bytes):
      40 73 41 07 80 88 ff ff 00 00 00 00 00 00 00 00  @sA.............
    backtrace:
      [&lt;0000000087736d2a&gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&lt;0000000060740f50&gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&lt;0000000083e8e205&gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&lt;000000008f2f414a&gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&lt;00000000de1cd4a0&gt;] vfs_write+0x216/0x4b0
      [&lt;00000000a2850200&gt;] ksys_write+0x71/0xf0
      [&lt;00000000de8e720b&gt;] __x64_sys_write+0x19/0x20
      [&lt;0000000018b12cbb&gt;] do_syscall_64+0x3f/0x90
      [&lt;00000000986ec465&gt;] entry_SYSCALL_64_after_hw…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hfjw-rcpx-5rv6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</id>
    <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-03T14:34:24.540444+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2023:2458"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</id>
    <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-03T14:34:24.541089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50738</id>
    <title>UBUNTU-CVE-2022-50738</title>
    <updated>2026-10-03T14:34:24.541320+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 79 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: vhost-vdpa: fix an iotlb memory leak Before commit 3d5698793897 ("vhost-vdpa: introduce asid based IOTLB") we called vhost_vdpa_iotlb_unmap(v, iotlb, 0ULL, 0ULL - 1) during release to free all the resources allocated when processing user IOTLB messages through vhost_vdpa_process_iotlb_update(). That commit changed the handling of IOTLB a bit, and we accidentally removed some code called during the release. We partially fixed this with commit 037d4305569a ("vhost-vdpa: call vhost_vdpa_cleanup during the release") but a potential memory leak is still there as showed by kmemleak if the application does not send VHOST_IOTLB_INVALIDATE or crashes:   unreferenced object 0xffff888007fbaa30 (size 16):     comm "blkio-bench", pid 914, jiffies 4294993521 (age 885.500s)     hex dump (first 16 bytes):       40 73 41 07 80 88 ff ff 00 00 00 00 00 00 00 00  @sA.............     backtrace:       [&lt;0000000087736d2a&gt;] kmem_cache_alloc_trace+0x142/0x1c0       [&lt;0000000060740f50&gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]       [&lt;0000000083e8e205&gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]       [&lt;000000008f2f414a&gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]       [&lt;00000000de1cd4a0&gt;] vfs_write+0x216/0x4b0       [&lt;00000000a2850200&gt;] ksys_write+0x71/0xf0       [&lt;00000000de8e720b&gt;] __x64_sys_write+0x19/0x20       [&lt;0000000018b12cbb&gt;] do_syscall_64+0x3f/0x90       [&lt;00000000986ec465&gt;] entry_SYSCALL_64_after_hwfram…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50738"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</id>
    <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T14:34:24.541462+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929"/>
  </entry>
</feed>
