<?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:59:26 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:19409 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:19409</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sr: Fix MAC comparison to be constant-time (CVE-2025-39702)
  * kernel: fs: fix UAF/GPF bug in nilfs_mdt_destroy (CVE-2022-50367)
  * kernel: crypto: xts - Handle EBUSY correctly (CVE-2023-53494)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sr: Fix MAC comparison to be constant-time (CVE-2025-39702)
  * kernel: fs: fix UAF/GPF bug in nilfs_mdt_destroy (CVE-2022-50367)
  * kernel: crypto: xts - Handle EBUSY correctly (CVE-2023-53494)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:19409</guid>
    </item>
    <item>
      <title>bdu:2025-15716</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15716</link>
      <description>bdu:2025-15716</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15716</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39702</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39702</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-2025-39702</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>EUVD-2026-347180</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347180</link>
      <description>EUVD-2026-347180</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347180</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39702</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39702</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: sr: Fix MAC comparison to be constant-time&lt;/p&gt;
&lt;p&gt;To prevent timing attacks, MACs need to be compared in constant time.
Use the appropriate helper function for this.&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;ipv6: sr: Fix MAC comparison to be constant-time&lt;/p&gt;
&lt;p&gt;To prevent timing attacks, MACs need to be compared in constant time.
Use the appropriate helper function for this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39702</guid>
    </item>
    <item>
      <title>GHSA-37gv-w6h3-7hm7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-37gv-w6h3-7hm7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: sr: Fix MAC comparison to be constant-time&lt;/p&gt;
&lt;p&gt;To prevent timing attacks, MACs need to be compared in constant time.
Use the appropriate helper function for this.&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;ipv6: sr: Fix MAC comparison to be constant-time&lt;/p&gt;
&lt;p&gt;To prevent timing attacks, MACs need to be compared in constant time.
Use the appropriate helper function for this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-37gv-w6h3-7hm7</guid>
    </item>
    <item>
      <title>ICSA-26-134-10 — Siemens SIMATIC</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-134-10</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_res-&amp;gt;hpo_dp_link_enc before using it&#13;
&#13;
[WHAT &amp;amp; HOW]&#13;
Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res&#13;
without initializing hpo_dp_link_enc and it is necessary to check for&#13;
null before dereferencing.&#13;
&#13;
This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;#34;ovl: support
encoding non-decodable file handles&amp;#34;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlay…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_res-&amp;gt;hpo_dp_link_enc before using it&#13;
&#13;
[WHAT &amp;amp; HOW]&#13;
Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res&#13;
without initializing hpo_dp_link_enc and it is necessary to check for&#13;
null before dereferencing.&#13;
&#13;
This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;#34;ovl: support
encoding non-decodable file handles&amp;#34;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlay…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-134-10</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-39702 — ipv6: sr: Fix MAC comparison to be constant-time</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-39702</link>
      <description>msrc_CVE-2025-39702</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-39702</guid>
    </item>
    <item>
      <title>NCSC-2026-0147 — Kwetsbaarheden verholpen in Siemens-producten</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0147</link>
      <description>NCSC-2026-0147</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0147</guid>
    </item>
    <item>
      <title>OESA-2026-1341 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1341</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-&amp;amp;gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-&amp;amp;gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obta…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-&amp;amp;gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-&amp;amp;gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obta…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1341</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20091-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20091-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/opensuse-su-2025:20091-1</guid>
    </item>
    <item>
      <title>RHSA-2025:19469 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:19469</link>
      <description>&lt;p&gt;kernel: ipv6: sr: Fix MAC comparison to be constant-time kernel: kernfs: Fix UAF in polling when open file is released&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: ipv6: sr: Fix MAC comparison to be constant-time kernel: kernfs: Fix UAF in polling when open file is released&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:19469</guid>
    </item>
    <item>
      <title>SSA-032379 — SSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-032379</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_res-&amp;gt;hpo_dp_link_enc before using it&#13;
&#13;
[WHAT &amp;amp; HOW]&#13;
Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res&#13;
without initializing hpo_dp_link_enc and it is necessary to check for&#13;
null before dereferencing.&#13;
&#13;
This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;#34;ovl: support
encoding non-decodable file handles&amp;#34;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlay…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
drm/amd/display: Check link_res-&amp;gt;hpo_dp_link_enc before using it&#13;
&#13;
[WHAT &amp;amp; HOW]&#13;
Functions dp_enable_link_phy and dp_disable_link_phy can pass link_res&#13;
without initializing hpo_dp_link_enc and it is necessary to check for&#13;
null before dereferencing.&#13;
&#13;
This fixes 2 FORWARD_NULL issues reported by Coverity. In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: relax assertions on failure to encode file handles&lt;/p&gt;
&lt;p&gt;Encoding file handles is usually performed by a filesystem &amp;gt;encode_fh()
method that may fail for various reasons.&lt;/p&gt;
&lt;p&gt;The legacy users of exportfs_encode_fh(), namely, nfsd and
name_to_handle_at(2) syscall are ready to cope with the possibility
of failure to encode a file handle.&lt;/p&gt;
&lt;p&gt;There are a few other users of exportfs_encode_{fh,fid}() that
currently have a WARN_ON() assertion when -&amp;gt;encode_fh() fails.
Relax those assertions because they are wrong.&lt;/p&gt;
&lt;p&gt;The second linked bug report states commit 16aac5ad1fa9 (&amp;#34;ovl: support
encoding non-decodable file handles&amp;#34;) in v6.6 as the regressing commit,
but this is not accurate.&lt;/p&gt;
&lt;p&gt;The aforementioned commit only increases the chances of the assertion
and allows triggering the assertion with the reproducer using overlayfs,
inotify and drop_caches.&lt;/p&gt;
&lt;p&gt;Triggering this assertion was always possible with other filesystems and
other reasons of -&amp;gt;encode_fh() failures and more particularly, it was
also possible with the exact same reproducer using overlay…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-032379</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:21040-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:21040-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:21040-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39702</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39702</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this.&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: Fix MAC comparison to be constant-time To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39702</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1988 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.&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 oder nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1988</guid>
    </item>
  </channel>
</rss>
