<?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>Mon, 05 Oct 2026 04:30:50 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15099</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15099</link>
      <description>bdu:2025-15099</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15099</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53056</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53056</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-2024-53056</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1102 — 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-1102</link>
      <description>certfr-2024-avi-1102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-1102</guid>
    </item>
    <item>
      <title>cnvd-2024-46416</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-46416</link>
      <description>cnvd-2024-46416</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-46416</guid>
    </item>
    <item>
      <title>EUVD-2026-320732</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320732</link>
      <description>EUVD-2026-320732</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320732</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53056</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53056</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()&lt;/p&gt;
&lt;p&gt;In mtk_crtc_create(), if the call to mbox_request_channel() fails then we
set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation,
we do not call cmdq_pkt_create().&lt;/p&gt;
&lt;p&gt;During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34;
is NULL first before calling cmdq_pkt_destroy().  Calling
cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and
it will result in a NULL pointer dereference.&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;drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()&lt;/p&gt;
&lt;p&gt;In mtk_crtc_create(), if the call to mbox_request_channel() fails then we
set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation,
we do not call cmdq_pkt_create().&lt;/p&gt;
&lt;p&gt;During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34;
is NULL first before calling cmdq_pkt_destroy().  Calling
cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and
it will result in a NULL pointer dereference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53056</guid>
    </item>
    <item>
      <title>GHSA-5ggj-xwvc-9x57</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5ggj-xwvc-9x57</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()&lt;/p&gt;
&lt;p&gt;In mtk_crtc_create(), if the call to mbox_request_channel() fails then we
set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation,
we do not call cmdq_pkt_create().&lt;/p&gt;
&lt;p&gt;During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34;
is NULL first before calling cmdq_pkt_destroy().  Calling
cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and
it will result in a NULL pointer dereference.&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;drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()&lt;/p&gt;
&lt;p&gt;In mtk_crtc_create(), if the call to mbox_request_channel() fails then we
set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation,
we do not call cmdq_pkt_create().&lt;/p&gt;
&lt;p&gt;During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34;
is NULL first before calling cmdq_pkt_destroy().  Calling
cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and
it will result in a NULL pointer dereference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5ggj-xwvc-9x57</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-53056 — drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-53056</link>
      <description>msrc_CVE-2024-53056</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-53056</guid>
    </item>
    <item>
      <title>OESA-2025-1110 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1110</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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1110</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:4314-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:4314-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:4314-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53056</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53056</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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy() In mtk_crtc_create(), if the call to mbox_request_channel() fails then we set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation, we do not call cmdq_pkt_create(). During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; is NULL first before calling cmdq_pkt_destroy().  Calling cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and it will result in a NULL pointer dereference.&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 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix potential NULL dereference in mtk_crtc_destroy() In mtk_crtc_create(), if the call to mbox_request_channel() fails then we set the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; pointer to NULL.  In that situation, we do not call cmdq_pkt_create(). During the cleanup, we need to check if the &amp;#34;mtk_crtc-&amp;gt;cmdq_client.chan&amp;#34; is NULL first before calling cmdq_pkt_destroy().  Calling cmdq_pkt_destroy() is unnecessary if we didn&amp;#39;t call cmdq_pkt_create() and it will result in a NULL pointer dereference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53056</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>
