<?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 14:48:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-08228</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-08228</link>
      <description>bdu:2024-08228</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-08228</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-44997</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-44997</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-44997</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0870 — 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-0870</link>
      <description>certfr-2024-avi-0870</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0870</guid>
    </item>
    <item>
      <title>EUVD-2026-346068</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346068</link>
      <description>EUVD-2026-346068</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346068</guid>
    </item>
    <item>
      <title>fkie_cve-2024-44997</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-44997</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()&lt;/p&gt;
&lt;p&gt;When there are multiple ap interfaces on one band and with WED on,
turning the interface down will cause a kernel panic on MT798X.&lt;/p&gt;
&lt;p&gt;Previously, cb_priv was freed in mtk_wed_setup_tc_block() without
marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too.&lt;/p&gt;
&lt;p&gt;Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL
in mtk_wed_setup_tc_block_cb().&lt;/p&gt;
&lt;p&gt;----------
Unable to handle kernel paging request at virtual address 0072460bca32b4f5
Call trace:
 mtk_wed_setup_tc_block_cb+0x4/0x38
 0xffffffc0794084bc
 tcf_block_playback_offloads+0x70/0x1e8
 tcf_block_unbind+0x6c/0xc8
...
---------&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: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()&lt;/p&gt;
&lt;p&gt;When there are multiple ap interfaces on one band and with WED on,
turning the interface down will cause a kernel panic on MT798X.&lt;/p&gt;
&lt;p&gt;Previously, cb_priv was freed in mtk_wed_setup_tc_block() without
marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too.&lt;/p&gt;
&lt;p&gt;Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL
in mtk_wed_setup_tc_block_cb().&lt;/p&gt;
&lt;p&gt;----------
Unable to handle kernel paging request at virtual address 0072460bca32b4f5
Call trace:
 mtk_wed_setup_tc_block_cb+0x4/0x38
 0xffffffc0794084bc
 tcf_block_playback_offloads+0x70/0x1e8
 tcf_block_unbind+0x6c/0xc8
...
---------&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-44997</guid>
    </item>
    <item>
      <title>GHSA-2jrr-ff5x-5jqg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2jrr-ff5x-5jqg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()&lt;/p&gt;
&lt;p&gt;When there are multiple ap interfaces on one band and with WED on,
turning the interface down will cause a kernel panic on MT798X.&lt;/p&gt;
&lt;p&gt;Previously, cb_priv was freed in mtk_wed_setup_tc_block() without
marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too.&lt;/p&gt;
&lt;p&gt;Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL
in mtk_wed_setup_tc_block_cb().&lt;/p&gt;
&lt;p&gt;----------
Unable to handle kernel paging request at virtual address 0072460bca32b4f5
Call trace:
 mtk_wed_setup_tc_block_cb+0x4/0x38
 0xffffffc0794084bc
 tcf_block_playback_offloads+0x70/0x1e8
 tcf_block_unbind+0x6c/0xc8
...
---------&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: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()&lt;/p&gt;
&lt;p&gt;When there are multiple ap interfaces on one band and with WED on,
turning the interface down will cause a kernel panic on MT798X.&lt;/p&gt;
&lt;p&gt;Previously, cb_priv was freed in mtk_wed_setup_tc_block() without
marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too.&lt;/p&gt;
&lt;p&gt;Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL
in mtk_wed_setup_tc_block_cb().&lt;/p&gt;
&lt;p&gt;----------
Unable to handle kernel paging request at virtual address 0072460bca32b4f5
Call trace:
 mtk_wed_setup_tc_block_cb+0x4/0x38
 0xffffffc0794084bc
 tcf_block_playback_offloads+0x70/0x1e8
 tcf_block_unbind+0x6c/0xc8
...
---------&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2jrr-ff5x-5jqg</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-44997 — net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-44997</link>
      <description>msrc_CVE-2024-44997</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-44997</guid>
    </item>
    <item>
      <title>OESA-2024-2325 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2325</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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&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:  ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  media: pci: cx23885: check cx23885_vdev_init() return  cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check.  Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
btrfs: make sure that WRITTEN is set on all metadata blocks&#13;
&#13;
We previously would call btrfs_check_leaf() if we had the check
integrity code enabled, which meant that we could only run the extended
leaf checks if we had WRITTEN set on the header flags.&#13;
&#13;
This leaves a gap in our checking, because we could end up with
corruption on disk where WRITTEN isn&amp;amp;apos;t set on the leaf, and then the
extended leaf checks don&amp;amp;apos;t get run which we rely on to validate all of
the item pointers to make sure we don&amp;amp;apos;t access memory outside of the
extent buffer.&#13;
&#13;
However, since 732fab95abe2 (&amp;amp;quot;btrfs: check-integrity: remove
CONFIG_BTRFS_FS_CHECK_INTEGRITY option&amp;amp;quot;) we no longer call
btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only
ever c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2325</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3551-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3551-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:3551-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-44997</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-44997</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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() When there are multiple ap interfaces on one band and with WED on, turning the interface down will cause a kernel panic on MT798X. Previously, cb_priv was freed in mtk_wed_setup_tc_block() without marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too. Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL in mtk_wed_setup_tc_block_cb(). ---------- Unable to handle kernel paging request at virtual address 0072460bca32b4f5 Call trace:  mtk_wed_setup_tc_block_cb+0x4/0x38  0xffffffc0794084bc  tcf_block_playback_offloads+0x70/0x1e8  tcf_block_unbind+0x6c/0xc8 ... ---------&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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() When there are multiple ap interfaces on one band and with WED on, turning the interface down will cause a kernel panic on MT798X. Previously, cb_priv was freed in mtk_wed_setup_tc_block() without marking NULL,and mtk_wed_setup_tc_block_cb() didn&amp;#39;t check the value, too. Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL in mtk_wed_setup_tc_block_cb(). ---------- Unable to handle kernel paging request at virtual address 0072460bca32b4f5 Call trace:  mtk_wed_setup_tc_block_cb+0x4/0x38  0xffffffc0794084bc  tcf_block_playback_offloads+0x70/0x1e8  tcf_block_unbind+0x6c/0xc8 ... ---------&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-44997</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2057 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service oder unspezifischer Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2057</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder weitere unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder weitere unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2057</guid>
    </item>
  </channel>
</rss>
