<?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 09:47:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07732</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07732</link>
      <description>bdu:2025-07732</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07732</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53210</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53210</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-53210</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0047 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</link>
      <description>certfr-2025-avi-0047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</guid>
    </item>
    <item>
      <title>EUVD-2026-313664</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313664</link>
      <description>EUVD-2026-313664</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313664</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53210</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53210</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()&lt;/p&gt;
&lt;p&gt;Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount
(skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount
at exit.
This results in skb memory leak in skb_queue_purge() and WARN_ON in
iucv_sock_destruct() during socket close. To fix this decrease
skb refcount by one if MSG_PEEK is set in order to prevent memory
leak and WARN_ON.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv]
CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W          6.10.0-rc7 #1
Hardware name: IBM 3931 A01 704 (z/VM 7.3.0)
Call Trace:
        [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]
        [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]
        [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550
        [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230
        [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40
        [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970
        [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0
        [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050
        [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360
        [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60
        [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380
        [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160
        [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98
        Last Breaking-Event-Addre…&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;s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()&lt;/p&gt;
&lt;p&gt;Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount
(skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount
at exit.
This results in skb memory leak in skb_queue_purge() and WARN_ON in
iucv_sock_destruct() during socket close. To fix this decrease
skb refcount by one if MSG_PEEK is set in order to prevent memory
leak and WARN_ON.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv]
CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W          6.10.0-rc7 #1
Hardware name: IBM 3931 A01 704 (z/VM 7.3.0)
Call Trace:
        [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]
        [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]
        [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550
        [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230
        [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40
        [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970
        [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0
        [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050
        [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360
        [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60
        [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380
        [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160
        [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98
        Last Breaking-Event-Addre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53210</guid>
    </item>
    <item>
      <title>GHSA-242f-ccpq-545j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-242f-ccpq-545j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()&lt;/p&gt;
&lt;p&gt;Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount
(skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount
at exit.
This results in skb memory leak in skb_queue_purge() and WARN_ON in
iucv_sock_destruct() during socket close. To fix this decrease
skb refcount by one if MSG_PEEK is set in order to prevent memory
leak and WARN_ON.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv]
CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W          6.10.0-rc7 #1
Hardware name: IBM 3931 A01 704 (z/VM 7.3.0)
Call Trace:
        [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]
        [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]
        [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550
        [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230
        [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40
        [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970
        [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0
        [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050
        [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360
        [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60
        [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380
        [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160
        [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98
        Last Breaking-Event-Addre…&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;s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()&lt;/p&gt;
&lt;p&gt;Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount
(skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount
at exit.
This results in skb memory leak in skb_queue_purge() and WARN_ON in
iucv_sock_destruct() during socket close. To fix this decrease
skb refcount by one if MSG_PEEK is set in order to prevent memory
leak and WARN_ON.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv]
CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W          6.10.0-rc7 #1
Hardware name: IBM 3931 A01 704 (z/VM 7.3.0)
Call Trace:
        [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]
        [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]
        [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550
        [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230
        [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40
        [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970
        [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0
        [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050
        [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360
        [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60
        [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380
        [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160
        [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98
        Last Breaking-Event-Addre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-242f-ccpq-545j</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-53210 — s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-53210</link>
      <description>msrc_CVE-2024-53210</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-53210</guid>
    </item>
    <item>
      <title>OESA-2025-1286 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1286</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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1286</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0117-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0117-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:0117-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53210</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53210</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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount (skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount at exit. This results in skb memory leak in skb_queue_purge() and WARN_ON in iucv_sock_destruct() during socket close. To fix this decrease skb refcount by one if MSG_PEEK is set in order to prevent memory leak and WARN_ON. WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv] CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W       6.10.0-rc7 #1 Hardware name: IBM 3931 A01 704 (z/VM 7.3.0) Call Trace:         [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]         [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]         [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550         [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230         [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40         [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970         [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0         [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050         [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360         [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60         [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380         [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160         [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98         Last Breaking-Event-Address:…&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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount (skb-&amp;gt;users) and iucv_sock_recvmsg() does not decrement skb refcount at exit. This results in skb memory leak in skb_queue_purge() and WARN_ON in iucv_sock_destruct() during socket close. To fix this decrease skb refcount by one if MSG_PEEK is set in order to prevent memory leak and WARN_ON. WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv] CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W       6.10.0-rc7 #1 Hardware name: IBM 3931 A01 704 (z/VM 7.3.0) Call Trace:         [&amp;lt;001587c682c4aa98&amp;gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv]         [&amp;lt;001587c682c4a9d0&amp;gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv]         [&amp;lt;001587c704117a32&amp;gt;] __sk_destruct+0x52/0x550         [&amp;lt;001587c704104a54&amp;gt;] __sock_release+0xa4/0x230         [&amp;lt;001587c704104c0c&amp;gt;] sock_close+0x2c/0x40         [&amp;lt;001587c702c5f5a8&amp;gt;] __fput+0x2e8/0x970         [&amp;lt;001587c7024148c4&amp;gt;] task_work_run+0x1c4/0x2c0         [&amp;lt;001587c7023b0716&amp;gt;] do_exit+0x996/0x1050         [&amp;lt;001587c7023b13aa&amp;gt;] do_group_exit+0x13a/0x360         [&amp;lt;001587c7023b1626&amp;gt;] __s390x_sys_exit_group+0x56/0x60         [&amp;lt;001587c7022bccca&amp;gt;] do_syscall+0x27a/0x380         [&amp;lt;001587c7049a6a0c&amp;gt;] __do_syscall+0x9c/0x160         [&amp;lt;001587c7049ce8a8&amp;gt;] system_call+0x70/0x98         Last Breaking-Event-Address:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53210</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>
