<?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 11:03:07 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12384</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12384</link>
      <description>bdu:2026-12384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12384</guid>
    </item>
    <item>
      <title>EUVD-2026-311273</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311273</link>
      <description>EUVD-2026-311273</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311273</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50506</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50506</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&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;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50506</guid>
    </item>
    <item>
      <title>GHSA-2p73-743m-m4r5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2p73-743m-m4r5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&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;drbd: only clone bio if we have a backing device&lt;/p&gt;
&lt;p&gt;Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a
bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from
drbd_request_prepare to drbd_req_new.&lt;/p&gt;
&lt;p&gt;The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is
not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when
the DRBD device is diskless), this leads to a null pointer deref.&lt;/p&gt;
&lt;p&gt;So, only allocate the private_bio if we actually have a disk. This is
also a small optimization, since we don&amp;#39;t clone the bio to only to
immediately free it again in the diskless case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2p73-743m-m4r5</guid>
    </item>
    <item>
      <title>RHSA-2022:8267 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:8267</link>
      <description>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: fix &amp;#39;struct pid&amp;#39; leaks in &amp;#39;dbgfs_target_ids_write()&amp;#39; kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: irqchip/gic-v3-its: Fix potential VPE leak on error kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: ethtool: do not perform operations on net devices being unregistered kernel: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() kernel: net: nexthop: fix null pointer dereference when IPv6 is not enabled kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34; kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: KVM: cmpxchg_gpte can write to pfns outside the userspace region ke…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: fix &amp;#39;struct pid&amp;#39; leaks in &amp;#39;dbgfs_target_ids_write()&amp;#39; kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: irqchip/gic-v3-its: Fix potential VPE leak on error kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: ptp: Fix possible memory leak in ptp_clock_register() kernel: ethtool: do not perform operations on net devices being unregistered kernel: ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce() kernel: net: nexthop: fix null pointer dereference when IPv6 is not enabled kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34; kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: KVM: cmpxchg_gpte can write to pfns outside the userspace region ke…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:8267</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50506</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50506</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drbd: only clone bio if we have a backing device Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from drbd_request_prepare to drbd_req_new. The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when the DRBD device is diskless), this leads to a null pointer deref. So, only allocate the private_bio if we actually have a disk. This is also a small optimization, since we don&amp;#39;t clone the bio to only to immediately free it again in the diskless case.&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drbd: only clone bio if we have a backing device Commit c347a787e34cb (drbd: set -&amp;gt;bi_bdev in drbd_req_new) moved a bio_set_dev call (which has since been removed) to &amp;#34;earlier&amp;#34;, from drbd_request_prepare to drbd_req_new. The problem is that this accesses device-&amp;gt;ldev-&amp;gt;backing_bdev, which is not NULL-checked at this point. When we don&amp;#39;t have an ldev (i.e. when the DRBD device is diskless), this leads to a null pointer deref. So, only allocate the private_bio if we actually have a disk. This is also a small optimization, since we don&amp;#39;t clone the bio to only to immediately free it again in the diskless case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50506</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2194 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2194</guid>
    </item>
  </channel>
</rss>
