<?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 20:52:22 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04384</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04384</link>
      <description>bdu:2025-04384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04384</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-344483</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344483</link>
      <description>EUVD-2026-344483</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344483</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47438</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47438</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&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;net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47438</guid>
    </item>
    <item>
      <title>GHSA-24vw-fq64-647q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-24vw-fq64-647q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&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;net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-24vw-fq64-647q</guid>
    </item>
    <item>
      <title>OESA-2024-1692 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1692</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: usb: fix possible use-after-free in smsc75xx_bind&#13;
&#13;
The commit 46a8b29c6306 (&amp;amp;quot;net: usb: fix memory leak in smsc75xx_bind&amp;amp;quot;)
fails to clean up the work scheduled in smsc75xx_reset-&amp;amp;gt;
smsc75xx_set_multicast, which leads to use-after-free if the work is
scheduled to start after the deallocation. In addition, this patch
also removes a dangling pointer - dev-&amp;amp;gt;data[0].&#13;
&#13;
This patch calls cancel_work_sync to cancel the scheduled work and set
the dangling pointer to NULL.(CVE-2021-47239)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
RDMA: Verify port when creating flow rule&#13;
&#13;
Validate port value provided by the user and with that remove no longer
needed validation by the driver.  The missing check in the mlx5_ib driver
could cause to the below oops.&#13;
&#13;
Call trace:
  _create_flow_rule+0x2d4/0xf28 [mlx5_ib]
  mlx5_ib_create_flow+0x2d0/0x5b0 [mlx5_ib]
  ib_uverbs_ex_create_flow+0x4cc/0x624 [ib_uverbs]
  ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xd4/0x150 [ib_uverbs]
  ib_uverbs_cmd_verbs.isra.7+0xb28/0xc50 [ib_uverbs]
  ib_uverbs_ioctl+0x158/0x1d0 [ib_uverbs]
  do_vfs_ioctl+0xd0/0xaf0
  ksys_ioctl+0x84/0xb4
  __arm64_sys_ioctl+0x28/0xc4
  el0_svc_common.constprop.3+0xa4/0x254
  el0_svc_handler+0x84/0xa0
  el0_svc+0x10/0x26c
 Code: b9401260 f9615681 51000400 8b001c20 (f9403c1a)(CVE-2021-47…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
net: usb: fix possible use-after-free in smsc75xx_bind&#13;
&#13;
The commit 46a8b29c6306 (&amp;amp;quot;net: usb: fix memory leak in smsc75xx_bind&amp;amp;quot;)
fails to clean up the work scheduled in smsc75xx_reset-&amp;amp;gt;
smsc75xx_set_multicast, which leads to use-after-free if the work is
scheduled to start after the deallocation. In addition, this patch
also removes a dangling pointer - dev-&amp;amp;gt;data[0].&#13;
&#13;
This patch calls cancel_work_sync to cancel the scheduled work and set
the dangling pointer to NULL.(CVE-2021-47239)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
RDMA: Verify port when creating flow rule&#13;
&#13;
Validate port value provided by the user and with that remove no longer
needed validation by the driver.  The missing check in the mlx5_ib driver
could cause to the below oops.&#13;
&#13;
Call trace:
  _create_flow_rule+0x2d4/0xf28 [mlx5_ib]
  mlx5_ib_create_flow+0x2d0/0x5b0 [mlx5_ib]
  ib_uverbs_ex_create_flow+0x4cc/0x624 [ib_uverbs]
  ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xd4/0x150 [ib_uverbs]
  ib_uverbs_cmd_verbs.isra.7+0xb28/0xc50 [ib_uverbs]
  ib_uverbs_ioctl+0x158/0x1d0 [ib_uverbs]
  do_vfs_ioctl+0xd0/0xaf0
  ksys_ioctl+0x84/0xb4
  __arm64_sys_ioctl+0x28/0xc4
  el0_svc_common.constprop.3+0xa4/0x254
  el0_svc_handler+0x84/0xa0
  el0_svc+0x10/0x26c
 Code: b9401260 f9615681 51000400 8b001c20 (f9403c1a)(CVE-2021-47…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1692</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-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-2024:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47438</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47438</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path Prior to this patch in case mlx5_core_destroy_cq() failed it returns without completing all destroy operations and that leads to memory leak. Instead, complete the destroy flow before return error. Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq() to be symmetrical with mlx5_core_create_cq(). kmemleak complains on: unreferenced object 0xc000000038625100 (size 64):   comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)   hex dump (first 32 bytes):     60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....     02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....   backtrace:     [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]     [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]     [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]     [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]     [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]     [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]     [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]     [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230 [mlx5_core]     [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300 [mlx5_core]     [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]     [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0/0x1b…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path Prior to this patch in case mlx5_core_destroy_cq() failed it returns without completing all destroy operations and that leads to memory leak. Instead, complete the destroy flow before return error. Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq() to be symmetrical with mlx5_core_create_cq(). kmemleak complains on: unreferenced object 0xc000000038625100 (size 64):   comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)   hex dump (first 32 bytes):     60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....     02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....   backtrace:     [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]     [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]     [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]     [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]     [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]     [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]     [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]     [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230 [mlx5_core]     [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300 [mlx5_core]     [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]     [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0/0x1b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47438</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1197 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</guid>
    </item>
  </channel>
</rss>
