<?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>Sun, 04 Oct 2026 12:24:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15052</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15052</link>
      <description>bdu:2025-15052</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15052</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53044</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53044</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-53044</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>cnvd-2024-46447</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-46447</link>
      <description>cnvd-2024-46447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-46447</guid>
    </item>
    <item>
      <title>EUVD-2026-346376</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346376</link>
      <description>EUVD-2026-346376</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346376</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53044</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53044</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()&lt;/p&gt;
&lt;p&gt;This command:&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: block dev insert failed: -EBUSY.&lt;/p&gt;
&lt;p&gt;fails because user space requests the same block index to be set for
both ingress and egress.&lt;/p&gt;
&lt;p&gt;[ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e
  (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this
  is a command from an old set of notes of mine which used to work, but
  alas, I did not scientifically bisect this ]&lt;/p&gt;
&lt;p&gt;The problem is not that it fails, but rather, that the second time
around, it fails differently (and irrecoverably):&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: dsa_core: Flow block cb is busy.&lt;/p&gt;
&lt;p&gt;[ another note: the extack is added by me for illustration purposes.
  the context of the problem is that clsact_init() obtains the same
  &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call
  tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the
  block-&amp;gt;ports xarray twice, thus failing the operation: once through
  the ingress block pointer, and once again through the egress block
  pointer. the problem itself is that when xa_insert() fails, we have
  emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the
  offload never sees a corresponding FLOW_BLOCK_UNBIND. ]&lt;/p&gt;
&lt;p&gt;Even correcting the bad user input, we still can…&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;net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()&lt;/p&gt;
&lt;p&gt;This command:&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: block dev insert failed: -EBUSY.&lt;/p&gt;
&lt;p&gt;fails because user space requests the same block index to be set for
both ingress and egress.&lt;/p&gt;
&lt;p&gt;[ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e
  (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this
  is a command from an old set of notes of mine which used to work, but
  alas, I did not scientifically bisect this ]&lt;/p&gt;
&lt;p&gt;The problem is not that it fails, but rather, that the second time
around, it fails differently (and irrecoverably):&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: dsa_core: Flow block cb is busy.&lt;/p&gt;
&lt;p&gt;[ another note: the extack is added by me for illustration purposes.
  the context of the problem is that clsact_init() obtains the same
  &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call
  tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the
  block-&amp;gt;ports xarray twice, thus failing the operation: once through
  the ingress block pointer, and once again through the egress block
  pointer. the problem itself is that when xa_insert() fails, we have
  emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the
  offload never sees a corresponding FLOW_BLOCK_UNBIND. ]&lt;/p&gt;
&lt;p&gt;Even correcting the bad user input, we still can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53044</guid>
    </item>
    <item>
      <title>GHSA-g4gg-7gqp-cf6m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g4gg-7gqp-cf6m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()&lt;/p&gt;
&lt;p&gt;This command:&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: block dev insert failed: -EBUSY.&lt;/p&gt;
&lt;p&gt;fails because user space requests the same block index to be set for
both ingress and egress.&lt;/p&gt;
&lt;p&gt;[ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e
  (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this
  is a command from an old set of notes of mine which used to work, but
  alas, I did not scientifically bisect this ]&lt;/p&gt;
&lt;p&gt;The problem is not that it fails, but rather, that the second time
around, it fails differently (and irrecoverably):&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: dsa_core: Flow block cb is busy.&lt;/p&gt;
&lt;p&gt;[ another note: the extack is added by me for illustration purposes.
  the context of the problem is that clsact_init() obtains the same
  &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call
  tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the
  block-&amp;gt;ports xarray twice, thus failing the operation: once through
  the ingress block pointer, and once again through the egress block
  pointer. the problem itself is that when xa_insert() fails, we have
  emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the
  offload never sees a corresponding FLOW_BLOCK_UNBIND. ]&lt;/p&gt;
&lt;p&gt;Even correcting the bad user input, we still can…&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;net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext()&lt;/p&gt;
&lt;p&gt;This command:&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: block dev insert failed: -EBUSY.&lt;/p&gt;
&lt;p&gt;fails because user space requests the same block index to be set for
both ingress and egress.&lt;/p&gt;
&lt;p&gt;[ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e
  (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this
  is a command from an old set of notes of mine which used to work, but
  alas, I did not scientifically bisect this ]&lt;/p&gt;
&lt;p&gt;The problem is not that it fails, but rather, that the second time
around, it fails differently (and irrecoverably):&lt;/p&gt;
&lt;p&gt;$ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact
Error: dsa_core: Flow block cb is busy.&lt;/p&gt;
&lt;p&gt;[ another note: the extack is added by me for illustration purposes.
  the context of the problem is that clsact_init() obtains the same
  &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call
  tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the
  block-&amp;gt;ports xarray twice, thus failing the operation: once through
  the ingress block pointer, and once again through the egress block
  pointer. the problem itself is that when xa_insert() fails, we have
  emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the
  offload never sees a corresponding FLOW_BLOCK_UNBIND. ]&lt;/p&gt;
&lt;p&gt;Even correcting the bad user input, we still can…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g4gg-7gqp-cf6m</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>UBUNTU-CVE-2024-53044</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53044</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext() This command: $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: block dev insert failed: -EBUSY. fails because user space requests the same block index to be set for both ingress and egress. [ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e   (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this   is a command from an old set of notes of mine which used to work, but   alas, I did not scientifically bisect this ] The problem is not that it fails, but rather, that the second time around, it fails differently (and irrecoverably): $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: dsa_core: Flow block cb is busy. [ another note: the extack is added by me for illustration purposes.   the context of the problem is that clsact_init() obtains the same   &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call   tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the   block-&amp;gt;ports xarray twice, thus failing the operation: once through   the ingress block pointer, and once again through the egress block   pointer. the problem itself is that when xa_insert() fails, we have   emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the   offload never sees a corresponding FLOW_BLOCK_UNBIND. ] Even correcting the bad user input, we still cannot recov…&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_api: fix xa_insert() error path in tcf_block_get_ext() This command: $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: block dev insert failed: -EBUSY. fails because user space requests the same block index to be set for both ingress and egress. [ side note, I don&amp;#39;t think it even failed prior to commit 913b47d3424e   (&amp;#34;net/sched: Introduce tc block netdev tracking infra&amp;#34;), because this   is a command from an old set of notes of mine which used to work, but   alas, I did not scientifically bisect this ] The problem is not that it fails, but rather, that the second time around, it fails differently (and irrecoverably): $ tc qdisc replace dev eth0 ingress_block 1 egress_block 1 clsact Error: dsa_core: Flow block cb is busy. [ another note: the extack is added by me for illustration purposes.   the context of the problem is that clsact_init() obtains the same   &amp;amp;q-&amp;gt;ingress_block pointer as &amp;amp;q-&amp;gt;egress_block, and since we call   tcf_block_get_ext() on both of them, &amp;#34;dev&amp;#34; will be added to the   block-&amp;gt;ports xarray twice, thus failing the operation: once through   the ingress block pointer, and once again through the egress block   pointer. the problem itself is that when xa_insert() fails, we have   emitted a FLOW_BLOCK_BIND command through ndo_setup_tc(), but the   offload never sees a corresponding FLOW_BLOCK_UNBIND. ] Even correcting the bad user input, we still cannot recov…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53044</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3509 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3509</guid>
    </item>
  </channel>
</rss>
