<?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>Fri, 02 Oct 2026 16:30:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04876</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04876</link>
      <description>bdu:2026-04876</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04876</guid>
    </item>
    <item>
      <title>EUVD-2026-310986</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310986</link>
      <description>EUVD-2026-310986</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310986</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50058</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50058</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vdpa_sim_blk: set number of address spaces and virtqueue groups&lt;/p&gt;
&lt;p&gt;Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two
new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to
initialize them for vdpa_sim_blk.&lt;/p&gt;
&lt;p&gt;When creating a new vdpa_sim_blk device this causes the kernel
to panic in this way:
    $ vdpa dev add mgmtdev vdpasim_blk name blk0
    BUG: kernel NULL pointer dereference, address: 0000000000000030
    ...
    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]
     vdpasim_map_range+0x91/0xd0 [vdpa_sim]
     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]
     ...&lt;/p&gt;
&lt;p&gt;This happens because vdpasim-&amp;gt;iommu[0] is not initialized when
dev_attr.nas is 0.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for
vdpa_sim_blk.&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;vdpa_sim_blk: set number of address spaces and virtqueue groups&lt;/p&gt;
&lt;p&gt;Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two
new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to
initialize them for vdpa_sim_blk.&lt;/p&gt;
&lt;p&gt;When creating a new vdpa_sim_blk device this causes the kernel
to panic in this way:
    $ vdpa dev add mgmtdev vdpasim_blk name blk0
    BUG: kernel NULL pointer dereference, address: 0000000000000030
    ...
    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]
     vdpasim_map_range+0x91/0xd0 [vdpa_sim]
     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]
     ...&lt;/p&gt;
&lt;p&gt;This happens because vdpasim-&amp;gt;iommu[0] is not initialized when
dev_attr.nas is 0.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for
vdpa_sim_blk.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50058</guid>
    </item>
    <item>
      <title>GHSA-q8cf-83hq-3865</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q8cf-83hq-3865</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vdpa_sim_blk: set number of address spaces and virtqueue groups&lt;/p&gt;
&lt;p&gt;Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two
new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to
initialize them for vdpa_sim_blk.&lt;/p&gt;
&lt;p&gt;When creating a new vdpa_sim_blk device this causes the kernel
to panic in this way:
    $ vdpa dev add mgmtdev vdpasim_blk name blk0
    BUG: kernel NULL pointer dereference, address: 0000000000000030
    ...
    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]
     vdpasim_map_range+0x91/0xd0 [vdpa_sim]
     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]
     ...&lt;/p&gt;
&lt;p&gt;This happens because vdpasim-&amp;gt;iommu[0] is not initialized when
dev_attr.nas is 0.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for
vdpa_sim_blk.&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;vdpa_sim_blk: set number of address spaces and virtqueue groups&lt;/p&gt;
&lt;p&gt;Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two
new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to
initialize them for vdpa_sim_blk.&lt;/p&gt;
&lt;p&gt;When creating a new vdpa_sim_blk device this causes the kernel
to panic in this way:
    $ vdpa dev add mgmtdev vdpasim_blk name blk0
    BUG: kernel NULL pointer dereference, address: 0000000000000030
    ...
    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]
    ...
    Call Trace:
     &amp;lt;TASK&amp;gt;
     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]
     vdpasim_map_range+0x91/0xd0 [vdpa_sim]
     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]
     ...&lt;/p&gt;
&lt;p&gt;This happens because vdpasim-&amp;gt;iommu[0] is not initialized when
dev_attr.nas is 0.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for
vdpa_sim_blk.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q8cf-83hq-3865</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>UBUNTU-CVE-2022-50058</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50058</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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vdpa_sim_blk: set number of address spaces and virtqueue groups Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to initialize them for vdpa_sim_blk. When creating a new vdpa_sim_blk device this causes the kernel to panic in this way:     $ vdpa dev add mgmtdev vdpasim_blk name blk0     BUG: kernel NULL pointer dereference, address: 0000000000000030     ...     RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]     ...     Call Trace:      &amp;lt;TASK&amp;gt;      vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]      vdpasim_map_range+0x91/0xd0 [vdpa_sim]      vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]      ... This happens because vdpasim-&amp;gt;iommu[0] is not initialized when dev_attr.nas is 0. Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for vdpa_sim_blk.&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 71 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vdpa_sim_blk: set number of address spaces and virtqueue groups Commit bda324fd037a (&amp;#34;vdpasim: control virtqueue support&amp;#34;) added two new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to initialize them for vdpa_sim_blk. When creating a new vdpa_sim_blk device this causes the kernel to panic in this way:     $ vdpa dev add mgmtdev vdpasim_blk name blk0     BUG: kernel NULL pointer dereference, address: 0000000000000030     ...     RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]     ...     Call Trace:      &amp;lt;TASK&amp;gt;      vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]      vdpasim_map_range+0x91/0xd0 [vdpa_sim]      vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]      ... This happens because vdpasim-&amp;gt;iommu[0] is not initialized when dev_attr.nas is 0. Let&amp;#39;s fix this issue by initializing both (nas, ngroups) to 1 for vdpa_sim_blk.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50058</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1350 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350</guid>
    </item>
  </channel>
</rss>
