<?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 07:19:31 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07749</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07749</link>
      <description>bdu:2025-07749</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07749</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53223</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53223</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-53223</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-313672</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313672</link>
      <description>EUVD-2026-313672</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313672</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53223</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53223</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs&lt;/p&gt;
&lt;p&gt;Base clocks are the first in being probed and are real dependencies of the
rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,
RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case,
when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the
following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138
 Modules linked in:
 CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0
 Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000
 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000
 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000
 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009
 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000
 ...
 Call Trace:
 [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4
 [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60
 [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4
 [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94
 [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138
 [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688
 [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c
 [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594
 [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c
 [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c
 [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c
 [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/…&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;clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs&lt;/p&gt;
&lt;p&gt;Base clocks are the first in being probed and are real dependencies of the
rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,
RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case,
when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the
following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138
 Modules linked in:
 CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0
 Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000
 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000
 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000
 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009
 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000
 ...
 Call Trace:
 [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4
 [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60
 [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4
 [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94
 [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138
 [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688
 [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c
 [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594
 [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c
 [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c
 [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c
 [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53223</guid>
    </item>
    <item>
      <title>GHSA-5xv2-6m9r-98p7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xv2-6m9r-98p7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs&lt;/p&gt;
&lt;p&gt;Base clocks are the first in being probed and are real dependencies of the
rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,
RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case,
when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the
following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138
 Modules linked in:
 CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0
 Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000
 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000
 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000
 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009
 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000
 ...
 Call Trace:
 [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4
 [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60
 [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4
 [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94
 [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138
 [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688
 [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c
 [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594
 [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c
 [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c
 [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c
 [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/…&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;clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs&lt;/p&gt;
&lt;p&gt;Base clocks are the first in being probed and are real dependencies of the
rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880,
RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case,
when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the
following warning appears:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138
 Modules linked in:
 CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0
 Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000
 80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000
 00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000
 203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009
 00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000
 ...
 Call Trace:
 [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4
 [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60
 [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4
 [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94
 [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138
 [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688
 [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c
 [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594
 [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c
 [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c
 [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c
 [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xv2-6m9r-98p7</guid>
    </item>
    <item>
      <title>OESA-2025-1093 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1093</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: dsa: improve shutdown sequence&lt;/p&gt;
&lt;p&gt;Alexander Sverdlin presents 2 problems during shutdown with the
lan9303 driver. One is specific to lan9303 and the other just happens
to reproduce there.&lt;/p&gt;
&lt;p&gt;The first problem is that lan9303 is unique among DSA drivers in that it
calls dev_get_drvdata() at &amp;amp;quot;arbitrary runtime&amp;amp;quot; (not probe, not shutdown,
not remove):&lt;/p&gt;
&lt;p&gt;phy_state_machine()
-&amp;amp;gt; ...
   -&amp;amp;gt; dsa_user_phy_read()
      -&amp;amp;gt; ds-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
         -&amp;amp;gt; lan9303_phy_read()
            -&amp;amp;gt; chip-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
               -&amp;amp;gt; lan9303_mdio_phy_read()
                  -&amp;amp;gt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: dsa: improve shutdown sequence&lt;/p&gt;
&lt;p&gt;Alexander Sverdlin presents 2 problems during shutdown with the
lan9303 driver. One is specific to lan9303 and the other just happens
to reproduce there.&lt;/p&gt;
&lt;p&gt;The first problem is that lan9303 is unique among DSA drivers in that it
calls dev_get_drvdata() at &amp;amp;quot;arbitrary runtime&amp;amp;quot; (not probe, not shutdown,
not remove):&lt;/p&gt;
&lt;p&gt;phy_state_machine()
-&amp;amp;gt; ...
   -&amp;amp;gt; dsa_user_phy_read()
      -&amp;amp;gt; ds-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
         -&amp;amp;gt; lan9303_phy_read()
            -&amp;amp;gt; chip-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
               -&amp;amp;gt; lan9303_mdio_phy_read()
                  -&amp;amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1093</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53223</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53223</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs Base clocks are the first in being probed and are real dependencies of the rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880, RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case, when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the following warning appears:  WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138  Modules linked in:  CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0  Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000  80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000  00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000  203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009  00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000  ...  Call Trace:  [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4  [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60  [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4  [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94  [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138  [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688  [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c  [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594  [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c  [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c  [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c  [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/0x6…&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: clk: ralink: mtmips: fix clocks probe order in oldest ralink SoCs Base clocks are the first in being probed and are real dependencies of the rest of fixed, factor and peripheral clocks. For old ralink SoCs RT2880, RT305x and RT3883 &amp;#39;xtal&amp;#39; must be defined first since in any other case, when fixed clocks are probed they are delayed until &amp;#39;xtal&amp;#39; is probed so the following warning appears:  WARNING: CPU: 0 PID: 0 at drivers/clk/ralink/clk-mtmips.c:499 rt3883_bus_recalc_rate+0x98/0x138  Modules linked in:  CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.43 #0  Stack : 805e58d0 00000000 00000004 8004f950 00000000 00000004 00000000 00000000  80669c54 80830000 80700000 805ae570 80670068 00000001 80669bf8 00000000  00000000 00000000 805ae570 80669b38 00000020 804db7dc 00000000 00000000  203a6d6d 80669b78 80669e48 70617773 00000000 805ae570 00000000 00000009  00000000 00000001 00000004 00000001 00000000 00000000 83fe43b0 00000000  ...  Call Trace:  [&amp;lt;800065d0&amp;gt;] show_stack+0x64/0xf4  [&amp;lt;804bca14&amp;gt;] dump_stack_lvl+0x38/0x60  [&amp;lt;800218ac&amp;gt;] __warn+0x94/0xe4  [&amp;lt;8002195c&amp;gt;] warn_slowpath_fmt+0x60/0x94  [&amp;lt;80259ff8&amp;gt;] rt3883_bus_recalc_rate+0x98/0x138  [&amp;lt;80254530&amp;gt;] __clk_register+0x568/0x688  [&amp;lt;80254838&amp;gt;] of_clk_hw_register+0x18/0x2c  [&amp;lt;8070b910&amp;gt;] rt2880_clk_of_clk_init_driver+0x18c/0x594  [&amp;lt;8070b628&amp;gt;] of_clk_init+0x1c0/0x23c  [&amp;lt;806fc448&amp;gt;] plat_time_init+0x58/0x18c  [&amp;lt;806fdaf0&amp;gt;] time_init+0x10/0x6c  [&amp;lt;806f9bc4&amp;gt;] start_kernel+0x458/0x6…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53223</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&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 und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
