<?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 10:03:42 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10433</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10433</link>
      <description>bdu:2026-10433</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10433</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53798</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53798</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53798</guid>
    </item>
    <item>
      <title>EUVD-2026-312262</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312262</link>
      <description>EUVD-2026-312262</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312262</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53798</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53798</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: Fix uninitialized number of lanes&lt;/p&gt;
&lt;p&gt;It is not possible to set the number of lanes when setting link modes
using the legacy IOCTL ethtool interface. Since &amp;#39;struct
ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive
an uninitialized number of lanes in &amp;#39;struct
ethtool_link_ksettings::lanes&amp;#39;.&lt;/p&gt;
&lt;p&gt;When this information is later queried from drivers, it results in the
ethtool code making decisions based on uninitialized memory, leading to
the following KMSAN splat [1]. In practice, this most likely only
happens with the tun driver that simply returns whatever it got in the
set operation.&lt;/p&gt;
&lt;p&gt;As far as I can tell, this uninitialized memory is not leaked to user
space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in
linkmodes_prepare_data().&lt;/p&gt;
&lt;p&gt;Fix by initializing the structure in the IOCTL path. Did not find any
more call sites that pass an uninitialized structure when calling
&amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;.&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
 ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640
 genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]
 genl_family_rcv_msg net/netlink/genetlink.…&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;ethtool: Fix uninitialized number of lanes&lt;/p&gt;
&lt;p&gt;It is not possible to set the number of lanes when setting link modes
using the legacy IOCTL ethtool interface. Since &amp;#39;struct
ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive
an uninitialized number of lanes in &amp;#39;struct
ethtool_link_ksettings::lanes&amp;#39;.&lt;/p&gt;
&lt;p&gt;When this information is later queried from drivers, it results in the
ethtool code making decisions based on uninitialized memory, leading to
the following KMSAN splat [1]. In practice, this most likely only
happens with the tun driver that simply returns whatever it got in the
set operation.&lt;/p&gt;
&lt;p&gt;As far as I can tell, this uninitialized memory is not leaked to user
space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in
linkmodes_prepare_data().&lt;/p&gt;
&lt;p&gt;Fix by initializing the structure in the IOCTL path. Did not find any
more call sites that pass an uninitialized structure when calling
&amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;.&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
 ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640
 genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]
 genl_family_rcv_msg net/netlink/genetlink.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53798</guid>
    </item>
    <item>
      <title>GHSA-rhrj-6hqh-9pgr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rhrj-6hqh-9pgr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: Fix uninitialized number of lanes&lt;/p&gt;
&lt;p&gt;It is not possible to set the number of lanes when setting link modes
using the legacy IOCTL ethtool interface. Since &amp;#39;struct
ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive
an uninitialized number of lanes in &amp;#39;struct
ethtool_link_ksettings::lanes&amp;#39;.&lt;/p&gt;
&lt;p&gt;When this information is later queried from drivers, it results in the
ethtool code making decisions based on uninitialized memory, leading to
the following KMSAN splat [1]. In practice, this most likely only
happens with the tun driver that simply returns whatever it got in the
set operation.&lt;/p&gt;
&lt;p&gt;As far as I can tell, this uninitialized memory is not leaked to user
space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in
linkmodes_prepare_data().&lt;/p&gt;
&lt;p&gt;Fix by initializing the structure in the IOCTL path. Did not find any
more call sites that pass an uninitialized structure when calling
&amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;.&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
 ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640
 genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]
 genl_family_rcv_msg net/netlink/genetlink.…&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;ethtool: Fix uninitialized number of lanes&lt;/p&gt;
&lt;p&gt;It is not possible to set the number of lanes when setting link modes
using the legacy IOCTL ethtool interface. Since &amp;#39;struct
ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive
an uninitialized number of lanes in &amp;#39;struct
ethtool_link_ksettings::lanes&amp;#39;.&lt;/p&gt;
&lt;p&gt;When this information is later queried from drivers, it results in the
ethtool code making decisions based on uninitialized memory, leading to
the following KMSAN splat [1]. In practice, this most likely only
happens with the tun driver that simply returns whatever it got in the
set operation.&lt;/p&gt;
&lt;p&gt;As far as I can tell, this uninitialized memory is not leaked to user
space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in
linkmodes_prepare_data().&lt;/p&gt;
&lt;p&gt;Fix by initializing the structure in the IOCTL path. Did not find any
more call sites that pass an uninitialized structure when calling
&amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;.&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]
 ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333
 ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640
 genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]
 genl_family_rcv_msg net/netlink/genetlink.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rhrj-6hqh-9pgr</guid>
    </item>
    <item>
      <title>RHSA-2024:3138 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3138</link>
      <description>&lt;p&gt;kernel: OOB writes in parse_hid_report_descriptor in drivers/input/tablet/gtco.c kernel: out of bounds read in drivers/media/usb/dvb-usb/technisat-usb2.c kernel: use-after-free in read in vt_do_kdgkb_ioctl kernel: a race out-of-bound read in vt kernel: improper input validation may lead to privilege escalation kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges kernel: use-after-free in l1oip timer handlers kernel: local privileges escalation in kernel/bpf/verifier.c kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: highmem: fix checks in __kmap_local_sched_{in,out} kernel: mm/slub: add missing TID updates on slab deactivation kernel: VMCI: Use threaded irqs instead of tasklets kernel: ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: jbd2: fix assertion &amp;#39;jh-&amp;gt;b_frozen_data == NULL&amp;#39; failure when journal aborted kernel: usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe kernel: media: dvbdev: adopts refcnt to avoid UAF kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value kernel: ext4: fix null-ptr-deref in ext4_write_info kernel: ext4: init quota for &amp;#39;old.inode&amp;#39; in &amp;#39;ext4_rename&amp;#39; kern…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: OOB writes in parse_hid_report_descriptor in drivers/input/tablet/gtco.c kernel: out of bounds read in drivers/media/usb/dvb-usb/technisat-usb2.c kernel: use-after-free in read in vt_do_kdgkb_ioctl kernel: a race out-of-bound read in vt kernel: improper input validation may lead to privilege escalation kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges kernel: use-after-free in l1oip timer handlers kernel: local privileges escalation in kernel/bpf/verifier.c kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: highmem: fix checks in __kmap_local_sched_{in,out} kernel: mm/slub: add missing TID updates on slab deactivation kernel: VMCI: Use threaded irqs instead of tasklets kernel: ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: jbd2: fix assertion &amp;#39;jh-&amp;gt;b_frozen_data == NULL&amp;#39; failure when journal aborted kernel: usb: host: Fix refcount leak in ehci_hcd_ppc_of_probe kernel: media: dvbdev: adopts refcnt to avoid UAF kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value kernel: ext4: fix null-ptr-deref in ext4_write_info kernel: ext4: init quota for &amp;#39;old.inode&amp;#39; in &amp;#39;ext4_rename&amp;#39; kern…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3138</guid>
    </item>
    <item>
      <title>RXSA-2024:3138 — Moderate: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rxsa-2024:3138</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rxsa-2024:3138</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53798</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53798</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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ethtool: Fix uninitialized number of lanes It is not possible to set the number of lanes when setting link modes using the legacy IOCTL ethtool interface. Since &amp;#39;struct ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive an uninitialized number of lanes in &amp;#39;struct ethtool_link_ksettings::lanes&amp;#39;. When this information is later queried from drivers, it results in the ethtool code making decisions based on uninitialized memory, leading to the following KMSAN splat [1]. In practice, this most likely only happens with the tun driver that simply returns whatever it got in the set operation. As far as I can tell, this uninitialized memory is not leaked to user space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in linkmodes_prepare_data(). Fix by initializing the structure in the IOCTL path. Did not find any more call sites that pass an uninitialized structure when calling &amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;. [1] BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline] BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333  ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]  ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333  ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640  genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]  genl_family_rcv_msg net/netlink/genetlink.c:1048…&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 110 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ethtool: Fix uninitialized number of lanes It is not possible to set the number of lanes when setting link modes using the legacy IOCTL ethtool interface. Since &amp;#39;struct ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive an uninitialized number of lanes in &amp;#39;struct ethtool_link_ksettings::lanes&amp;#39;. When this information is later queried from drivers, it results in the ethtool code making decisions based on uninitialized memory, leading to the following KMSAN splat [1]. In practice, this most likely only happens with the tun driver that simply returns whatever it got in the set operation. As far as I can tell, this uninitialized memory is not leaked to user space thanks to the &amp;#39;ethtool_ops-&amp;gt;cap_link_lanes_supported&amp;#39; check in linkmodes_prepare_data(). Fix by initializing the structure in the IOCTL path. Did not find any more call sites that pass an uninitialized structure when calling &amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;. [1] BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline] BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333  ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]  ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333  ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640  genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]  genl_family_rcv_msg net/netlink/genetlink.c:1048…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53798</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765</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-2765</guid>
    </item>
  </channel>
</rss>
