<?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 08:00:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05191</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05191</link>
      <description>bdu:2026-05191</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05191</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38591</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38591</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-38591</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0787 — 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-2025-avi-0787</link>
      <description>certfr-2025-avi-0787</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0787</guid>
    </item>
    <item>
      <title>EUVD-2026-367467</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367467</link>
      <description>EUVD-2026-367467</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367467</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38591</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38591</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject narrower access to pointer ctx fields&lt;/p&gt;
&lt;p&gt;The following BPF program, simplified from a syzkaller repro, causes a
kernel warning:&lt;/p&gt;
&lt;p&gt;r0 = *(u8 *)(r1 + 169);
    exit;&lt;/p&gt;
&lt;p&gt;With pointer field sk being at offset 168 in __sk_buff. This access is
detected as a narrower read in bpf_skb_is_valid_access because it
doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed
and later proceeds to bpf_convert_ctx_access. Note that for the
&amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off
is aligned, so the cnt may not be 0 because it matches the
offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,
the target_size stays 0 and the verifier errors with a kernel warning:&lt;/p&gt;
&lt;p&gt;verifier bug: error during ctx access conversion(1)&lt;/p&gt;
&lt;p&gt;This patch fixes that to return a proper &amp;#34;invalid bpf_context access
off=X size=Y&amp;#34; error on the load instruction.&lt;/p&gt;
&lt;p&gt;The same issue affects multiple other fields in context structures that
allow narrow access. Some other non-affected fields (for sk_msg,
sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for
consistency.&lt;/p&gt;
&lt;p&gt;Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which
used to be about a different bug, fixed in
commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions
in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs,
the new crash and repro didn&amp;#39;t get reported to the mailing lis…&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;bpf: Reject narrower access to pointer ctx fields&lt;/p&gt;
&lt;p&gt;The following BPF program, simplified from a syzkaller repro, causes a
kernel warning:&lt;/p&gt;
&lt;p&gt;r0 = *(u8 *)(r1 + 169);
    exit;&lt;/p&gt;
&lt;p&gt;With pointer field sk being at offset 168 in __sk_buff. This access is
detected as a narrower read in bpf_skb_is_valid_access because it
doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed
and later proceeds to bpf_convert_ctx_access. Note that for the
&amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off
is aligned, so the cnt may not be 0 because it matches the
offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,
the target_size stays 0 and the verifier errors with a kernel warning:&lt;/p&gt;
&lt;p&gt;verifier bug: error during ctx access conversion(1)&lt;/p&gt;
&lt;p&gt;This patch fixes that to return a proper &amp;#34;invalid bpf_context access
off=X size=Y&amp;#34; error on the load instruction.&lt;/p&gt;
&lt;p&gt;The same issue affects multiple other fields in context structures that
allow narrow access. Some other non-affected fields (for sk_msg,
sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for
consistency.&lt;/p&gt;
&lt;p&gt;Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which
used to be about a different bug, fixed in
commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions
in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs,
the new crash and repro didn&amp;#39;t get reported to the mailing lis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38591</guid>
    </item>
    <item>
      <title>GHSA-cgjw-h652-c9q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cgjw-h652-c9q2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject narrower access to pointer ctx fields&lt;/p&gt;
&lt;p&gt;The following BPF program, simplified from a syzkaller repro, causes a
kernel warning:&lt;/p&gt;
&lt;p&gt;r0 = *(u8 *)(r1 + 169);
    exit;&lt;/p&gt;
&lt;p&gt;With pointer field sk being at offset 168 in __sk_buff. This access is
detected as a narrower read in bpf_skb_is_valid_access because it
doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed
and later proceeds to bpf_convert_ctx_access. Note that for the
&amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off
is aligned, so the cnt may not be 0 because it matches the
offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,
the target_size stays 0 and the verifier errors with a kernel warning:&lt;/p&gt;
&lt;p&gt;verifier bug: error during ctx access conversion(1)&lt;/p&gt;
&lt;p&gt;This patch fixes that to return a proper &amp;#34;invalid bpf_context access
off=X size=Y&amp;#34; error on the load instruction.&lt;/p&gt;
&lt;p&gt;The same issue affects multiple other fields in context structures that
allow narrow access. Some other non-affected fields (for sk_msg,
sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for
consistency.&lt;/p&gt;
&lt;p&gt;Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which
used to be about a different bug, fixed in
commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions
in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs,
the new crash and repro didn&amp;#39;t get reported to the mailing lis…&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;bpf: Reject narrower access to pointer ctx fields&lt;/p&gt;
&lt;p&gt;The following BPF program, simplified from a syzkaller repro, causes a
kernel warning:&lt;/p&gt;
&lt;p&gt;r0 = *(u8 *)(r1 + 169);
    exit;&lt;/p&gt;
&lt;p&gt;With pointer field sk being at offset 168 in __sk_buff. This access is
detected as a narrower read in bpf_skb_is_valid_access because it
doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed
and later proceeds to bpf_convert_ctx_access. Note that for the
&amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off
is aligned, so the cnt may not be 0 because it matches the
offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,
the target_size stays 0 and the verifier errors with a kernel warning:&lt;/p&gt;
&lt;p&gt;verifier bug: error during ctx access conversion(1)&lt;/p&gt;
&lt;p&gt;This patch fixes that to return a proper &amp;#34;invalid bpf_context access
off=X size=Y&amp;#34; error on the load instruction.&lt;/p&gt;
&lt;p&gt;The same issue affects multiple other fields in context structures that
allow narrow access. Some other non-affected fields (for sk_msg,
sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for
consistency.&lt;/p&gt;
&lt;p&gt;Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which
used to be about a different bug, fixed in
commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions
in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs,
the new crash and repro didn&amp;#39;t get reported to the mailing lis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cgjw-h652-c9q2</guid>
    </item>
    <item>
      <title>ICSA-26-209-04 — Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-209-04</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-209-04</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38591 — bpf: Reject narrower access to pointer ctx fields</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38591</link>
      <description>msrc_CVE-2025-38591</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38591</guid>
    </item>
    <item>
      <title>OESA-2026-1759 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1759</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;iommu/s390: Implement blocking domain&lt;/p&gt;
&lt;p&gt;This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling.  With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.(CVE-2024-53232)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix two issues in iommu_copy_struct_from_user()&lt;/p&gt;
&lt;p&gt;In the review for iommu_copy_struct_to_user() helper, Matt pointed out that
a NULL pointer should be rejected prior to dereferencing it:
https://lore.kernel.org/all/(CVE-2025-37900)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: Avoid race in open_cached_dir with lease breaks&lt;/p&gt;
&lt;p&gt;A pre-existing valid cfid returned from find_or_create_cached_dir might
race with a lease break, meaning open_cached_dir doesn&amp;amp;apos;t consider it
valid,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;iommu/s390: Implement blocking domain&lt;/p&gt;
&lt;p&gt;This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling.  With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.(CVE-2024-53232)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix two issues in iommu_copy_struct_from_user()&lt;/p&gt;
&lt;p&gt;In the review for iommu_copy_struct_to_user() helper, Matt pointed out that
a NULL pointer should be rejected prior to dereferencing it:
https://lore.kernel.org/all/(CVE-2025-37900)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: Avoid race in open_cached_dir with lease breaks&lt;/p&gt;
&lt;p&gt;A pre-existing valid cfid returned from find_or_create_cached_dir might
race with a lease break, meaning open_cached_dir doesn&amp;amp;apos;t consider it
valid,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1759</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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:20081-1</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03272-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03272-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:03272-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38591</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38591</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: bpf: Reject narrower access to pointer ctx fields The following BPF program, simplified from a syzkaller repro, causes a kernel warning:     r0 = *(u8 *)(r1 + 169);     exit; With pointer field sk being at offset 168 in __sk_buff. This access is detected as a narrower read in bpf_skb_is_valid_access because it doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed and later proceeds to bpf_convert_ctx_access. Note that for the &amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off is aligned, so the cnt may not be 0 because it matches the offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However, the target_size stays 0 and the verifier errors with a kernel warning:     verifier bug: error during ctx access conversion(1) This patch fixes that to return a proper &amp;#34;invalid bpf_context access off=X size=Y&amp;#34; error on the load instruction. The same issue affects multiple other fields in context structures that allow narrow access. Some other non-affected fields (for sk_msg, sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for consistency. Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which used to be about a different bug, fixed in commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs, the new crash and repro didn&amp;#39;t get reported to the mailing list.&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: bpf: Reject narrower access to pointer ctx fields The following BPF program, simplified from a syzkaller repro, causes a kernel warning:     r0 = *(u8 *)(r1 + 169);     exit; With pointer field sk being at offset 168 in __sk_buff. This access is detected as a narrower read in bpf_skb_is_valid_access because it doesn&amp;#39;t match offsetof(struct __sk_buff, sk). It is therefore allowed and later proceeds to bpf_convert_ctx_access. Note that for the &amp;#34;is_narrower_load&amp;#34; case in the convert_ctx_accesses(), the insn-&amp;gt;off is aligned, so the cnt may not be 0 because it matches the offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However, the target_size stays 0 and the verifier errors with a kernel warning:     verifier bug: error during ctx access conversion(1) This patch fixes that to return a proper &amp;#34;invalid bpf_context access off=X size=Y&amp;#34; error on the load instruction. The same issue affects multiple other fields in context structures that allow narrow access. Some other non-affected fields (for sk_msg, sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for consistency. Note this syzkaller crash was reported in the &amp;#34;Closes&amp;#34; link below, which used to be about a different bug, fixed in commit fce7bd8e385a (&amp;#34;bpf/verifier: Handle BPF_LOAD_ACQ instructions in insn_def_regno()&amp;#34;). Because syzbot somehow confused the two bugs, the new crash and repro didn&amp;#39;t get reported to the mailing list.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38591</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1869 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1869</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1869</guid>
    </item>
  </channel>
</rss>
