<?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>Sun, 04 Oct 2026 03:30:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05902</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05902</link>
      <description>bdu:2026-05902</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05902</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53421</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53421</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53421</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>EUVD-2026-323454</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323454</link>
      <description>EUVD-2026-323454</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323454</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53421</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53421</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&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;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53421</guid>
    </item>
    <item>
      <title>GHSA-63xc-pmjj-q4vj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-63xc-pmjj-q4vj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&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;blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()&lt;/p&gt;
&lt;p&gt;When blkg_alloc() is called to allocate a blkcg_gq structure
with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within
blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync.
The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup:
Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by
commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using
cgroup rstat&amp;#34;).&lt;/p&gt;
&lt;p&gt;Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly
re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This
can lead to a kernel panic due to NULL pointer access of the blkg
pointer. The missing initialization of sync is less problematic and
can be a problem in a debug kernel due to missing lockdep initialization.&lt;/p&gt;
&lt;p&gt;Fix these problems by re-initializing them after memory clearing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-63xc-pmjj-q4vj</guid>
    </item>
    <item>
      <title>msrc_CVE-2023-53421 — blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2023-53421</link>
      <description>msrc_CVE-2023-53421</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2023-53421</guid>
    </item>
    <item>
      <title>RHSA-2023:7077 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:7077</link>
      <description>&lt;p&gt;kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait() in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c kernel: Rate limit overflow messages in r8152 in intr_callback kernel: use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c kernel: tun: avoid double free in tun_free_netdev kernel: double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: KVM: x86/mmu: race condition in direct_page_fault() kernel: memory leak in ttusb_dec_exit_dvb() in media/usb/ttusb-dec/ttusb_dec.c kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: mm/mempolicy: fix mpol_new leak in shared_policy_replace kernel: LSM: general protection fault in legacy_parse_param kernel: SUNRPC: Trap RDMA segment overflows kernel: mm/page_owner: use strscpy() instead of strlcpy() kernel: nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags kernel: cipso: Fix data-races around sysctl. kernel: cgroup: Use separate src/dst nodes when preloading css_sets for migration kernel: tick/nohz: unexport __init-annotated tick_nohz_full_setup() kernel: device property: fix of nod…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait() in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c kernel: Rate limit overflow messages in r8152 in intr_callback kernel: use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c kernel: tun: avoid double free in tun_free_netdev kernel: double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: KVM: x86/mmu: race condition in direct_page_fault() kernel: memory leak in ttusb_dec_exit_dvb() in media/usb/ttusb-dec/ttusb_dec.c kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: mm/mempolicy: fix mpol_new leak in shared_policy_replace kernel: LSM: general protection fault in legacy_parse_param kernel: SUNRPC: Trap RDMA segment overflows kernel: mm/page_owner: use strscpy() instead of strlcpy() kernel: nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags kernel: cipso: Fix data-races around sysctl. kernel: cgroup: Use separate src/dst nodes when preloading css_sets for migration kernel: tick/nohz: unexport __init-annotated tick_nohz_full_setup() kernel: device property: fix of nod…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:7077</guid>
    </item>
    <item>
      <title>RHSA-2024:1404 — Red Hat Security Advisory: kernel security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:1404</link>
      <description>&lt;p&gt;kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait() in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c kernel: nfp: use-after-free in area_cache_get() kernel: Rate limit overflow messages in r8152 in intr_callback kernel: tun: avoid double free in tun_free_netdev kernel: double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c kernel: vmwgfx: integer overflow in vmwgfx_execbuf.c kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context kernel: null-ptr-deref vulnerabilities in sl_tx_timeout in drivers/net/slip kernel: KVM: x86/mmu: race condition in direct_page_fault() kernel: memory leak in ttusb_dec_exit_dvb() in media/usb/ttusb-dec/ttusb_dec.c kernel: kernfs: fix potential NULL dereference in __kernfs_remove kernel: denial of service in tipc_conn_close kernel: NULL pointer dereference in can_rcv_filter kernel: Slab-out-of-bound read in compare_netdev_and_ip kernel: use-after-free in sch_qfq network scheduler kernel: vmwgfx: reference count issue leads to use-after-free in surface handling kernel: Out-Of-Bounds Read vulnerability in smbCalcSize kernel: OOB Access in smb2_dump_detail kernel: inactive elements in nft_pipapo_walk kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event&amp;#39;s read_size kernel: use-after-free in IPv4 IGMP kernel: refcount leak in ctnetlink_create_conntrack() kernel: lib/s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: out-of-bounds write in hw_atl_utils_fw_rpc_wait() in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c kernel: nfp: use-after-free in area_cache_get() kernel: Rate limit overflow messages in r8152 in intr_callback kernel: tun: avoid double free in tun_free_netdev kernel: double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c kernel: vmwgfx: integer overflow in vmwgfx_execbuf.c kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context kernel: null-ptr-deref vulnerabilities in sl_tx_timeout in drivers/net/slip kernel: KVM: x86/mmu: race condition in direct_page_fault() kernel: memory leak in ttusb_dec_exit_dvb() in media/usb/ttusb-dec/ttusb_dec.c kernel: kernfs: fix potential NULL dereference in __kernfs_remove kernel: denial of service in tipc_conn_close kernel: NULL pointer dereference in can_rcv_filter kernel: Slab-out-of-bound read in compare_netdev_and_ip kernel: use-after-free in sch_qfq network scheduler kernel: vmwgfx: reference count issue leads to use-after-free in surface handling kernel: Out-Of-Bounds Read vulnerability in smbCalcSize kernel: OOB Access in smb2_dump_detail kernel: inactive elements in nft_pipapo_walk kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event&amp;#39;s read_size kernel: use-after-free in IPv4 IGMP kernel: refcount leak in ctnetlink_create_conntrack() kernel: lib/s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:1404</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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-2025:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53421</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53421</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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq structure with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync. The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup: Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using cgroup rstat&amp;#34;). Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This can lead to a kernel panic due to NULL pointer access of the blkg pointer. The missing initialization of sync is less problematic and can be a problem in a debug kernel due to missing lockdep initialization. Fix these problems by re-initializing them after memory clearing.&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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() When blkg_alloc() is called to allocate a blkcg_gq structure with the associated blkg_iostat_set&amp;#39;s, there are 2 fields within blkg_iostat_set that requires proper initialization - blkg &amp;amp; sync. The former field was introduced by commit 3b8cc6298724 (&amp;#34;blk-cgroup: Optimize blkcg_rstat_flush()&amp;#34;) while the later one was introduced by commit f73316482977 (&amp;#34;blk-cgroup: reimplement basic IO stats using cgroup rstat&amp;#34;). Unfortunately those fields in the blkg_iostat_set&amp;#39;s are not properly re-initialized when they are cleared in v1&amp;#39;s blkcg_reset_stats(). This can lead to a kernel panic due to NULL pointer access of the blkg pointer. The missing initialization of sync is less problematic and can be a problem in a debug kernel due to missing lockdep initialization. Fix these problems by re-initializing them after memory clearing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53421</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2092 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2092</guid>
    </item>
  </channel>
</rss>
