<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 15:12:06 +0000</lastBuildDate>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-311408</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311408</link>
      <description>EUVD-2026-311408</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311408</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50738</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50738</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost-vdpa: fix an iotlb memory leak&lt;/p&gt;
&lt;p&gt;Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;)
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.&lt;/p&gt;
&lt;p&gt;We partially fixed this with commit 037d4305569a (&amp;#34;vhost-vdpa: call
vhost_vdpa_cleanup during the release&amp;#34;) but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888007fbaa30 (size 16):
    comm &amp;#34;blkio-bench&amp;#34;, 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:
      [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0
      [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0
      [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20
      [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90
      [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hw…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost-vdpa: fix an iotlb memory leak&lt;/p&gt;
&lt;p&gt;Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;)
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.&lt;/p&gt;
&lt;p&gt;We partially fixed this with commit 037d4305569a (&amp;#34;vhost-vdpa: call
vhost_vdpa_cleanup during the release&amp;#34;) but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888007fbaa30 (size 16):
    comm &amp;#34;blkio-bench&amp;#34;, 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:
      [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0
      [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0
      [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20
      [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90
      [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hw…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50738</guid>
    </item>
    <item>
      <title>GHSA-hfjw-rcpx-5rv6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hfjw-rcpx-5rv6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost-vdpa: fix an iotlb memory leak&lt;/p&gt;
&lt;p&gt;Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;)
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.&lt;/p&gt;
&lt;p&gt;We partially fixed this with commit 037d4305569a (&amp;#34;vhost-vdpa: call
vhost_vdpa_cleanup during the release&amp;#34;) but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888007fbaa30 (size 16):
    comm &amp;#34;blkio-bench&amp;#34;, 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:
      [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0
      [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0
      [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20
      [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90
      [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hw…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost-vdpa: fix an iotlb memory leak&lt;/p&gt;
&lt;p&gt;Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;)
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.&lt;/p&gt;
&lt;p&gt;We partially fixed this with commit 037d4305569a (&amp;#34;vhost-vdpa: call
vhost_vdpa_cleanup during the release&amp;#34;) but a potential memory leak is
still there as showed by kmemleak if the application does not send
VHOST_IOTLB_INVALIDATE or crashes:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888007fbaa30 (size 16):
    comm &amp;#34;blkio-bench&amp;#34;, 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:
      [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0
      [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]
      [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]
      [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]
      [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0
      [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0
      [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20
      [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90
      [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hw…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hfjw-rcpx-5rv6</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;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-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:2458</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50738</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50738</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost-vdpa: fix an iotlb memory leak Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;) 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 (&amp;#34;vhost-vdpa: call vhost_vdpa_cleanup during the release&amp;#34;) 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 &amp;#34;blkio-bench&amp;#34;, 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:       [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0       [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]       [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]       [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]       [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0       [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0       [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20       [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90       [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hwfram…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost-vdpa: fix an iotlb memory leak Before commit 3d5698793897 (&amp;#34;vhost-vdpa: introduce asid based IOTLB&amp;#34;) 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 (&amp;#34;vhost-vdpa: call vhost_vdpa_cleanup during the release&amp;#34;) 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 &amp;#34;blkio-bench&amp;#34;, 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:       [&amp;lt;0000000087736d2a&amp;gt;] kmem_cache_alloc_trace+0x142/0x1c0       [&amp;lt;0000000060740f50&amp;gt;] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa]       [&amp;lt;0000000083e8e205&amp;gt;] vhost_chr_write_iter+0xc0/0x4a0 [vhost]       [&amp;lt;000000008f2f414a&amp;gt;] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa]       [&amp;lt;00000000de1cd4a0&amp;gt;] vfs_write+0x216/0x4b0       [&amp;lt;00000000a2850200&amp;gt;] ksys_write+0x71/0xf0       [&amp;lt;00000000de8e720b&amp;gt;] __x64_sys_write+0x19/0x20       [&amp;lt;0000000018b12cbb&amp;gt;] do_syscall_64+0x3f/0x90       [&amp;lt;00000000986ec465&amp;gt;] entry_SYSCALL_64_after_hwfram…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50738</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
