<?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 19:06:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01090</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01090</link>
      <description>bdu:2025-01090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01090</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41010</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-41010</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0779 — 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-0779</link>
      <description>certfr-2024-avi-0779</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0779</guid>
    </item>
    <item>
      <title>cnvd-2024-33691</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-33691</link>
      <description>cnvd-2024-33691</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-33691</guid>
    </item>
    <item>
      <title>EUVD-2026-345904</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345904</link>
      <description>EUVD-2026-345904</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345904</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41010</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41010</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&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: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41010</guid>
    </item>
    <item>
      <title>GHSA-7rc8-rqg8-27m3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7rc8-rqg8-27m3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&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: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7rc8-rqg8-27m3</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-41010 — bpf: Fix too early release of tcx_entry</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-41010</link>
      <description>msrc_CVE-2024-41010</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-41010</guid>
    </item>
    <item>
      <title>OESA-2024-1960 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1960</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
efi: libstub: only free priv.runtime_map when allocated&#13;
&#13;
priv.runtime_map is only allocated when efi_novamap is not set.
Otherwise, it is an uninitialized value.  In the error path, it is freed
unconditionally.  Avoid passing an uninitialized value to free_pool.
Free priv.runtime_map only when it was allocated.&#13;
&#13;
This bug was discovered and resolved using Coverity Static Analysis
Security Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
fpga: region: add owner module and take its refcount&#13;
&#13;
The current implementation of the fpga region assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the region
during programming if the parent device does not have a driver.&#13;
&#13;
To address this problem, add a module owner pointer to the fpga_region
struct and use it to take the module&amp;amp;apos;s refcount. Modify the functions for
registering a region to take an additional owner module parameter and
rename them to avoid conflicts. Use the old function names for helper
macros that automatically set the module that registers the region as the
owner. This ensures compatibility with existing low…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
efi: libstub: only free priv.runtime_map when allocated&#13;
&#13;
priv.runtime_map is only allocated when efi_novamap is not set.
Otherwise, it is an uninitialized value.  In the error path, it is freed
unconditionally.  Avoid passing an uninitialized value to free_pool.
Free priv.runtime_map only when it was allocated.&#13;
&#13;
This bug was discovered and resolved using Coverity Static Analysis
Security Testing (SAST) by Synopsys, Inc.(CVE-2024-33619)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
fpga: region: add owner module and take its refcount&#13;
&#13;
The current implementation of the fpga region assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the region
during programming if the parent device does not have a driver.&#13;
&#13;
To address this problem, add a module owner pointer to the fpga_region
struct and use it to take the module&amp;amp;apos;s refcount. Modify the functions for
registering a region to take an additional owner module parameter and
rename them to avoid conflicts. Use the old function names for helper
macros that automatically set the module that registers the region as the
owner. This ensures compatibility with existing low…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1960</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3194-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3194-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:3194-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41010</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix too early release of tcx_entry Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported an issue that the tcx_entry can be released too early leading to a use after free (UAF) when an active old-style ingress or clsact qdisc with a shared tc block is later replaced by another ingress or clsact instance. Essentially, the sequence to trigger the UAF (one example) can be as follows:   1. A network namespace is created   2. An ingress qdisc is created. This allocates a tcx_entry, and      &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the      same time, a tcf block with index 1 is created.   3. chain0 is attached to the tcf block. chain0 must be connected to      the block linked to the ingress qdisc to later reach the function      tcf_chain0_head_change_cb_del() which triggers the UAF.   4. Create and graft a clsact qdisc. This causes the ingress qdisc      created in step 1 to be removed, thus freeing the previously linked      tcx_entry:      rtnetlink_rcv_msg()        =&amp;gt; tc_modify_qdisc()          =&amp;gt; qdisc_create()            =&amp;gt; clsact_init() [a]          =&amp;gt; qdisc_graft()            =&amp;gt; qdisc_destroy()              =&amp;gt; __qdisc_destroy()                =&amp;gt; ingress_destroy() [b]                  =&amp;gt; tcx_entry_free()                    =&amp;gt; kfree_rcu() // tcx_entry freed   5. Finally, the network namespace is closed. This registers the      cleanup_net worker, and during…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix too early release of tcx_entry Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported an issue that the tcx_entry can be released too early leading to a use after free (UAF) when an active old-style ingress or clsact qdisc with a shared tc block is later replaced by another ingress or clsact instance. Essentially, the sequence to trigger the UAF (one example) can be as follows:   1. A network namespace is created   2. An ingress qdisc is created. This allocates a tcx_entry, and      &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the      same time, a tcf block with index 1 is created.   3. chain0 is attached to the tcf block. chain0 must be connected to      the block linked to the ingress qdisc to later reach the function      tcf_chain0_head_change_cb_del() which triggers the UAF.   4. Create and graft a clsact qdisc. This causes the ingress qdisc      created in step 1 to be removed, thus freeing the previously linked      tcx_entry:      rtnetlink_rcv_msg()        =&amp;gt; tc_modify_qdisc()          =&amp;gt; qdisc_create()            =&amp;gt; clsact_init() [a]          =&amp;gt; qdisc_graft()            =&amp;gt; qdisc_destroy()              =&amp;gt; __qdisc_destroy()                =&amp;gt; ingress_destroy() [b]                  =&amp;gt; tcx_entry_free()                    =&amp;gt; kfree_rcu() // tcx_entry freed   5. Finally, the network namespace is closed. This registers the      cleanup_net worker, and during…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41010</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1646 — Linux Kernel: Mehrere Schwachstellen ermöglichen Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1646</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1646</guid>
    </item>
  </channel>
</rss>
