<?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 17:34:19 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05117</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05117</link>
      <description>bdu:2026-05117</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05117</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — 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-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-344968</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344968</link>
      <description>EUVD-2026-344968</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344968</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50755</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50755</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udf: Avoid double brelse() in udf_rename()&lt;/p&gt;
&lt;p&gt;syzbot reported a warning like below [1]:&lt;/p&gt;
&lt;p&gt;VFS: brelse: Trying to free free buffer
WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 invalidate_bh_lru+0x99/0x150
 smp_call_function_many_cond+0xe2a/0x10c0
 ? generic_remap_file_range_prep+0x50/0x50
 ? __brelse+0xa0/0xa0
 ? __mutex_lock+0x21c/0x12d0
 ? smp_call_on_cpu+0x250/0x250
 ? rcu_read_lock_sched_held+0xb/0x60
 ? lock_release+0x587/0x810
 ? __brelse+0xa0/0xa0
 ? generic_remap_file_range_prep+0x50/0x50
 on_each_cpu_cond_mask+0x3c/0x80
 blkdev_flush_mapping+0x13a/0x2f0
 blkdev_put_whole+0xd3/0xf0
 blkdev_put+0x222/0x760
 deactivate_locked_super+0x96/0x160
 deactivate_super+0xda/0x100
 cleanup_mnt+0x222/0x3d0
 task_work_run+0x149/0x240
 ? task_work_cancel+0x30/0x30
 do_exit+0xb29/0x2a40
 ? reacquire_held_locks+0x4a0/0x4a0
 ? do_raw_spin_lock+0x12a/0x2b0
 ? mm_update_next_owner+0x7c0/0x7c0
 ? rwlock_bug.part.0+0x90/0x90
 ? zap_other_threads+0x234/0x2d0
 do_group_exit+0xd0/0x2a0
 __x64_sys_exit_group+0x3a/0x50
 do_syscall_64+0x34/0xb0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;
&lt;p&gt;The cause of the issue is that brelse() is called on both ofibh.sbh
and ofibh.ebh by udf_find_entry() when it returns NULL.  However,
brelse() is called by udf_rename(), too.  So, b_count on buffer_head
becomes unbalanced.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not calling brelse() by udf_rename()
when udf_find_…&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;udf: Avoid double brelse() in udf_rename()&lt;/p&gt;
&lt;p&gt;syzbot reported a warning like below [1]:&lt;/p&gt;
&lt;p&gt;VFS: brelse: Trying to free free buffer
WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 invalidate_bh_lru+0x99/0x150
 smp_call_function_many_cond+0xe2a/0x10c0
 ? generic_remap_file_range_prep+0x50/0x50
 ? __brelse+0xa0/0xa0
 ? __mutex_lock+0x21c/0x12d0
 ? smp_call_on_cpu+0x250/0x250
 ? rcu_read_lock_sched_held+0xb/0x60
 ? lock_release+0x587/0x810
 ? __brelse+0xa0/0xa0
 ? generic_remap_file_range_prep+0x50/0x50
 on_each_cpu_cond_mask+0x3c/0x80
 blkdev_flush_mapping+0x13a/0x2f0
 blkdev_put_whole+0xd3/0xf0
 blkdev_put+0x222/0x760
 deactivate_locked_super+0x96/0x160
 deactivate_super+0xda/0x100
 cleanup_mnt+0x222/0x3d0
 task_work_run+0x149/0x240
 ? task_work_cancel+0x30/0x30
 do_exit+0xb29/0x2a40
 ? reacquire_held_locks+0x4a0/0x4a0
 ? do_raw_spin_lock+0x12a/0x2b0
 ? mm_update_next_owner+0x7c0/0x7c0
 ? rwlock_bug.part.0+0x90/0x90
 ? zap_other_threads+0x234/0x2d0
 do_group_exit+0xd0/0x2a0
 __x64_sys_exit_group+0x3a/0x50
 do_syscall_64+0x34/0xb0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;
&lt;p&gt;The cause of the issue is that brelse() is called on both ofibh.sbh
and ofibh.ebh by udf_find_entry() when it returns NULL.  However,
brelse() is called by udf_rename(), too.  So, b_count on buffer_head
becomes unbalanced.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not calling brelse() by udf_rename()
when udf_find_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50755</guid>
    </item>
    <item>
      <title>GHSA-4xw5-xvv7-qcv6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4xw5-xvv7-qcv6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;udf: Avoid double brelse() in udf_rename()&lt;/p&gt;
&lt;p&gt;syzbot reported a warning like below [1]:&lt;/p&gt;
&lt;p&gt;VFS: brelse: Trying to free free buffer
WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 invalidate_bh_lru+0x99/0x150
 smp_call_function_many_cond+0xe2a/0x10c0
 ? generic_remap_file_range_prep+0x50/0x50
 ? __brelse+0xa0/0xa0
 ? __mutex_lock+0x21c/0x12d0
 ? smp_call_on_cpu+0x250/0x250
 ? rcu_read_lock_sched_held+0xb/0x60
 ? lock_release+0x587/0x810
 ? __brelse+0xa0/0xa0
 ? generic_remap_file_range_prep+0x50/0x50
 on_each_cpu_cond_mask+0x3c/0x80
 blkdev_flush_mapping+0x13a/0x2f0
 blkdev_put_whole+0xd3/0xf0
 blkdev_put+0x222/0x760
 deactivate_locked_super+0x96/0x160
 deactivate_super+0xda/0x100
 cleanup_mnt+0x222/0x3d0
 task_work_run+0x149/0x240
 ? task_work_cancel+0x30/0x30
 do_exit+0xb29/0x2a40
 ? reacquire_held_locks+0x4a0/0x4a0
 ? do_raw_spin_lock+0x12a/0x2b0
 ? mm_update_next_owner+0x7c0/0x7c0
 ? rwlock_bug.part.0+0x90/0x90
 ? zap_other_threads+0x234/0x2d0
 do_group_exit+0xd0/0x2a0
 __x64_sys_exit_group+0x3a/0x50
 do_syscall_64+0x34/0xb0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;
&lt;p&gt;The cause of the issue is that brelse() is called on both ofibh.sbh
and ofibh.ebh by udf_find_entry() when it returns NULL.  However,
brelse() is called by udf_rename(), too.  So, b_count on buffer_head
becomes unbalanced.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not calling brelse() by udf_rename()
when udf_find_…&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;udf: Avoid double brelse() in udf_rename()&lt;/p&gt;
&lt;p&gt;syzbot reported a warning like below [1]:&lt;/p&gt;
&lt;p&gt;VFS: brelse: Trying to free free buffer
WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0
...
Call Trace:
 &amp;lt;TASK&amp;gt;
 invalidate_bh_lru+0x99/0x150
 smp_call_function_many_cond+0xe2a/0x10c0
 ? generic_remap_file_range_prep+0x50/0x50
 ? __brelse+0xa0/0xa0
 ? __mutex_lock+0x21c/0x12d0
 ? smp_call_on_cpu+0x250/0x250
 ? rcu_read_lock_sched_held+0xb/0x60
 ? lock_release+0x587/0x810
 ? __brelse+0xa0/0xa0
 ? generic_remap_file_range_prep+0x50/0x50
 on_each_cpu_cond_mask+0x3c/0x80
 blkdev_flush_mapping+0x13a/0x2f0
 blkdev_put_whole+0xd3/0xf0
 blkdev_put+0x222/0x760
 deactivate_locked_super+0x96/0x160
 deactivate_super+0xda/0x100
 cleanup_mnt+0x222/0x3d0
 task_work_run+0x149/0x240
 ? task_work_cancel+0x30/0x30
 do_exit+0xb29/0x2a40
 ? reacquire_held_locks+0x4a0/0x4a0
 ? do_raw_spin_lock+0x12a/0x2b0
 ? mm_update_next_owner+0x7c0/0x7c0
 ? rwlock_bug.part.0+0x90/0x90
 ? zap_other_threads+0x234/0x2d0
 do_group_exit+0xd0/0x2a0
 __x64_sys_exit_group+0x3a/0x50
 do_syscall_64+0x34/0xb0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;
&lt;p&gt;The cause of the issue is that brelse() is called on both ofibh.sbh
and ofibh.ebh by udf_find_entry() when it returns NULL.  However,
brelse() is called by udf_rename(), too.  So, b_count on buffer_head
becomes unbalanced.&lt;/p&gt;
&lt;p&gt;This patch fixes the issue by not calling brelse() by udf_rename()
when udf_find_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4xw5-xvv7-qcv6</guid>
    </item>
    <item>
      <title>OESA-2026-1231 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1231</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()&lt;/p&gt;
&lt;p&gt;When executing SMP task failed, the smp_execute_task_sg() calls del_timer()
to delete &amp;amp;quot;slow_task-&amp;amp;gt;timer&amp;amp;quot;. However, if the timer handler
sas_task_internal_timedout() is running, the del_timer() in
smp_execute_task_sg() will not stop it and a UAF will happen. The process
is shown below:&lt;/p&gt;
&lt;p&gt;(thread 1)               |        (thread 2)
smp_execute_task_sg()          | sas_task_internal_timedout()
 ...                           |
 del_timer()                   |
 ...                           |  ...
 sas_free_task(task)           |
  kfree(task-&amp;amp;gt;slow_task) //FREE|
                               |  task-&amp;amp;gt;slow_task-&amp;amp;gt;... //USE&lt;/p&gt;
&lt;p&gt;Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure
the timer handler have finished before the &amp;amp;quot;task-&amp;amp;gt;slow_task&amp;amp;quot; is
deallocated.(CVE-2022-50422)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: associate skb with a device at tx&lt;/p&gt;
&lt;p&gt;Syzkaller triggered flow dissector warning with the following:&lt;/p&gt;
&lt;p&gt;r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;amp;(0x7f0000000000), 0xc0802, 0x0)
ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;amp;(0x7f00000000c0))
ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;amp;(0x7f0000000240)={0x2, &amp;amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]})
pwritev(r0, &amp;amp;amp;(0x7f0000…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: libsas: Fix use-after-free bug in smp_execute_task_sg()&lt;/p&gt;
&lt;p&gt;When executing SMP task failed, the smp_execute_task_sg() calls del_timer()
to delete &amp;amp;quot;slow_task-&amp;amp;gt;timer&amp;amp;quot;. However, if the timer handler
sas_task_internal_timedout() is running, the del_timer() in
smp_execute_task_sg() will not stop it and a UAF will happen. The process
is shown below:&lt;/p&gt;
&lt;p&gt;(thread 1)               |        (thread 2)
smp_execute_task_sg()          | sas_task_internal_timedout()
 ...                           |
 del_timer()                   |
 ...                           |  ...
 sas_free_task(task)           |
  kfree(task-&amp;amp;gt;slow_task) //FREE|
                               |  task-&amp;amp;gt;slow_task-&amp;amp;gt;... //USE&lt;/p&gt;
&lt;p&gt;Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure
the timer handler have finished before the &amp;amp;quot;task-&amp;amp;gt;slow_task&amp;amp;quot; is
deallocated.(CVE-2022-50422)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: associate skb with a device at tx&lt;/p&gt;
&lt;p&gt;Syzkaller triggered flow dissector warning with the following:&lt;/p&gt;
&lt;p&gt;r0 = openat$ppp(0xffffffffffffff9c, &amp;amp;amp;(0x7f0000000000), 0xc0802, 0x0)
ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &amp;amp;amp;(0x7f00000000c0))
ioctl$PPPIOCSACTIVE(r0, 0x40107446, &amp;amp;amp;(0x7f0000000240)={0x2, &amp;amp;amp;(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]})
pwritev(r0, &amp;amp;amp;(0x7f0000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1231</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-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-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50755</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50755</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace:  &amp;lt;TASK&amp;gt;  invalidate_bh_lru+0x99/0x150  smp_call_function_many_cond+0xe2a/0x10c0  ? generic_remap_file_range_prep+0x50/0x50  ? __brelse+0xa0/0xa0  ? __mutex_lock+0x21c/0x12d0  ? smp_call_on_cpu+0x250/0x250  ? rcu_read_lock_sched_held+0xb/0x60  ? lock_release+0x587/0x810  ? __brelse+0xa0/0xa0  ? generic_remap_file_range_prep+0x50/0x50  on_each_cpu_cond_mask+0x3c/0x80  blkdev_flush_mapping+0x13a/0x2f0  blkdev_put_whole+0xd3/0xf0  blkdev_put+0x222/0x760  deactivate_locked_super+0x96/0x160  deactivate_super+0xda/0x100  cleanup_mnt+0x222/0x3d0  task_work_run+0x149/0x240  ? task_work_cancel+0x30/0x30  do_exit+0xb29/0x2a40  ? reacquire_held_locks+0x4a0/0x4a0  ? do_raw_spin_lock+0x12a/0x2b0  ? mm_update_next_owner+0x7c0/0x7c0  ? rwlock_bug.part.0+0x90/0x90  ? zap_other_threads+0x234/0x2d0  do_group_exit+0xd0/0x2a0  __x64_sys_exit_group+0x3a/0x50  do_syscall_64+0x34/0xb0  entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL.  However, brelse() is called by udf_rename(), too.  So, b_count on buffer_head becomes unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace:  &amp;lt;TASK&amp;gt;  invalidate_bh_lru+0x99/0x150  smp_call_function_many_cond+0xe2a/0x10c0  ? generic_remap_file_range_prep+0x50/0x50  ? __brelse+0xa0/0xa0  ? __mutex_lock+0x21c/0x12d0  ? smp_call_on_cpu+0x250/0x250  ? rcu_read_lock_sched_held+0xb/0x60  ? lock_release+0x587/0x810  ? __brelse+0xa0/0xa0  ? generic_remap_file_range_prep+0x50/0x50  on_each_cpu_cond_mask+0x3c/0x80  blkdev_flush_mapping+0x13a/0x2f0  blkdev_put_whole+0xd3/0xf0  blkdev_put+0x222/0x760  deactivate_locked_super+0x96/0x160  deactivate_super+0xda/0x100  cleanup_mnt+0x222/0x3d0  task_work_run+0x149/0x240  ? task_work_cancel+0x30/0x30  do_exit+0xb29/0x2a40  ? reacquire_held_locks+0x4a0/0x4a0  ? do_raw_spin_lock+0x12a/0x2b0  ? mm_update_next_owner+0x7c0/0x7c0  ? rwlock_bug.part.0+0x90/0x90  ? zap_other_threads+0x234/0x2d0  do_group_exit+0xd0/0x2a0  __x64_sys_exit_group+0x3a/0x50  do_syscall_64+0x34/0xb0  entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it returns NULL.  However, brelse() is called by udf_rename(), too.  So, b_count on buffer_head becomes unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50755</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
