<?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 13:51:37 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01745</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01745</link>
      <description>bdu:2025-01745</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01745</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-46735</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-46735</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-46735</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>cnvd-2024-39286</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-39286</link>
      <description>cnvd-2024-39286</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-39286</guid>
    </item>
    <item>
      <title>EUVD-2026-313257</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313257</link>
      <description>EUVD-2026-313257</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313257</guid>
    </item>
    <item>
      <title>fkie_cve-2024-46735</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-46735</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()&lt;/p&gt;
&lt;p&gt;When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the
first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers
WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference
issue.&lt;/p&gt;
&lt;p&gt;Fix it by adding the check in ublk_ctrl_start_recovery() and return
immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000028
  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ? __die+0x20/0x70
   ? page_fault_oops+0x75/0x170
   ? exc_page_fault+0x64/0x140
   ? asm_exc_page_fault+0x22/0x30
   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180
   ublk_ctrl_uring_cmd+0x4f7/0x6c0
   ? pick_next_task_idle+0x26/0x40
   io_uring_cmd+0x9a/0x1b0
   io_issue_sqe+0x193/0x3f0
   io_wq_submit_work+0x9b/0x390
   io_worker_handle_work+0x165/0x360
   io_wq_worker+0xcb/0x2f0
   ? finish_task_switch.isra.0+0x203/0x290
   ? finish_task_switch.isra.0+0x203/0x290
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork+0x2d/0x50
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&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;ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()&lt;/p&gt;
&lt;p&gt;When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the
first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers
WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference
issue.&lt;/p&gt;
&lt;p&gt;Fix it by adding the check in ublk_ctrl_start_recovery() and return
immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000028
  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ? __die+0x20/0x70
   ? page_fault_oops+0x75/0x170
   ? exc_page_fault+0x64/0x140
   ? asm_exc_page_fault+0x22/0x30
   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180
   ublk_ctrl_uring_cmd+0x4f7/0x6c0
   ? pick_next_task_idle+0x26/0x40
   io_uring_cmd+0x9a/0x1b0
   io_issue_sqe+0x193/0x3f0
   io_wq_submit_work+0x9b/0x390
   io_worker_handle_work+0x165/0x360
   io_wq_worker+0xcb/0x2f0
   ? finish_task_switch.isra.0+0x203/0x290
   ? finish_task_switch.isra.0+0x203/0x290
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork+0x2d/0x50
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-46735</guid>
    </item>
    <item>
      <title>GHSA-h642-rg9x-ww4c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h642-rg9x-ww4c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()&lt;/p&gt;
&lt;p&gt;When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the
first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers
WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference
issue.&lt;/p&gt;
&lt;p&gt;Fix it by adding the check in ublk_ctrl_start_recovery() and return
immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000028
  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ? __die+0x20/0x70
   ? page_fault_oops+0x75/0x170
   ? exc_page_fault+0x64/0x140
   ? asm_exc_page_fault+0x22/0x30
   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180
   ublk_ctrl_uring_cmd+0x4f7/0x6c0
   ? pick_next_task_idle+0x26/0x40
   io_uring_cmd+0x9a/0x1b0
   io_issue_sqe+0x193/0x3f0
   io_wq_submit_work+0x9b/0x390
   io_worker_handle_work+0x165/0x360
   io_wq_worker+0xcb/0x2f0
   ? finish_task_switch.isra.0+0x203/0x290
   ? finish_task_switch.isra.0+0x203/0x290
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork+0x2d/0x50
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&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;ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()&lt;/p&gt;
&lt;p&gt;When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the
first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers
WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference
issue.&lt;/p&gt;
&lt;p&gt;Fix it by adding the check in ublk_ctrl_start_recovery() and return
immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000028
  RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180
  Call Trace:
   &amp;lt;TASK&amp;gt;
   ? __die+0x20/0x70
   ? page_fault_oops+0x75/0x170
   ? exc_page_fault+0x64/0x140
   ? asm_exc_page_fault+0x22/0x30
   ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180
   ublk_ctrl_uring_cmd+0x4f7/0x6c0
   ? pick_next_task_idle+0x26/0x40
   io_uring_cmd+0x9a/0x1b0
   io_issue_sqe+0x193/0x3f0
   io_wq_submit_work+0x9b/0x390
   io_worker_handle_work+0x165/0x360
   io_wq_worker+0xcb/0x2f0
   ? finish_task_switch.isra.0+0x203/0x290
   ? finish_task_switch.isra.0+0x203/0x290
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork+0x2d/0x50
   ? __pfx_io_wq_worker+0x10/0x10
   ret_from_fork_asm+0x1a/0x30
   &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h642-rg9x-ww4c</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-46735 — ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-46735</link>
      <description>msrc_CVE-2024-46735</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-46735</guid>
    </item>
    <item>
      <title>OESA-2024-2367 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2367</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;
drm/amd/display: Add NULL pointer check for kzalloc&#13;
&#13;
[Why &amp;amp;amp; How]
Check return pointer of kzalloc before using it.(CVE-2024-42122)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mm: gup: stop abusing try_grab_folio&#13;
&#13;
A kernel warning was reported when pinning folio in CMA memory when
launching SEV virtual machine.  The splat looks like:&#13;
&#13;
[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520
[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6
[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520
[  464.325515] Call Trace:
[  464.325520]  &amp;amp;lt;TASK&amp;amp;gt;
[  464.325523]  ? __get_user_pages+0x423/0x520
[  464.325528]  ? __warn+0x81/0x130
[  464.325536]  ? __get_user_pages+0x423/0x520
[  464.325541]  ? report_bug+0x171/0x1a0
[  464.325549]  ? handle_bug+0x3c/0x70
[  464.325554]  ? exc_invalid_op+0x17/0x70
[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20
[  464.325567]  ? __get_user_pages+0x423/0x520
[  464.325575]  __gup_longterm_locked+0x212/0x7a0
[  464.325583]  internal_get_user_pages_fast+0xfb/0x190
[  464.325590]  pin_user_pages_fast+0x47/0x60
[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]
[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]&#13;
&#13;
Per the analysis done by yangge, when starting the SEV virtual machine, it…&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;
drm/amd/display: Add NULL pointer check for kzalloc&#13;
&#13;
[Why &amp;amp;amp; How]
Check return pointer of kzalloc before using it.(CVE-2024-42122)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mm: gup: stop abusing try_grab_folio&#13;
&#13;
A kernel warning was reported when pinning folio in CMA memory when
launching SEV virtual machine.  The splat looks like:&#13;
&#13;
[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520
[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6
[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520
[  464.325515] Call Trace:
[  464.325520]  &amp;amp;lt;TASK&amp;amp;gt;
[  464.325523]  ? __get_user_pages+0x423/0x520
[  464.325528]  ? __warn+0x81/0x130
[  464.325536]  ? __get_user_pages+0x423/0x520
[  464.325541]  ? report_bug+0x171/0x1a0
[  464.325549]  ? handle_bug+0x3c/0x70
[  464.325554]  ? exc_invalid_op+0x17/0x70
[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20
[  464.325567]  ? __get_user_pages+0x423/0x520
[  464.325575]  __gup_longterm_locked+0x212/0x7a0
[  464.325583]  internal_get_user_pages_fast+0xfb/0x190
[  464.325590]  pin_user_pages_fast+0x47/0x60
[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]
[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]&#13;
&#13;
Per the analysis done by yangge, when starting the SEV virtual machine, it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2367</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-46735</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46735</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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference issue. Fix it by adding the check in ublk_ctrl_start_recovery() and return immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.   BUG: kernel NULL pointer dereference, address: 0000000000000028   RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180   Call Trace:    &amp;lt;TASK&amp;gt;    ? __die+0x20/0x70    ? page_fault_oops+0x75/0x170    ? exc_page_fault+0x64/0x140    ? asm_exc_page_fault+0x22/0x30    ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180    ublk_ctrl_uring_cmd+0x4f7/0x6c0    ? pick_next_task_idle+0x26/0x40    io_uring_cmd+0x9a/0x1b0    io_issue_sqe+0x193/0x3f0    io_wq_submit_work+0x9b/0x390    io_worker_handle_work+0x165/0x360    io_wq_worker+0xcb/0x2f0    ? finish_task_switch.isra.0+0x203/0x290    ? finish_task_switch.isra.0+0x203/0x290    ? __pfx_io_wq_worker+0x10/0x10    ret_from_fork+0x2d/0x50    ? __pfx_io_wq_worker+0x10/0x10    ret_from_fork_asm+0x1a/0x30    &amp;lt;/TASK&amp;gt;&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 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ublk_drv: fix NULL pointer dereference in ublk_ctrl_start_recovery() When two UBLK_CMD_START_USER_RECOVERY commands are submitted, the first one sets &amp;#39;ubq-&amp;gt;ubq_daemon&amp;#39; to NULL, and the second one triggers WARN in ublk_queue_reinit() and subsequently a NULL pointer dereference issue. Fix it by adding the check in ublk_ctrl_start_recovery() and return immediately in case of zero &amp;#39;ub-&amp;gt;nr_queues_ready&amp;#39;.   BUG: kernel NULL pointer dereference, address: 0000000000000028   RIP: 0010:ublk_ctrl_start_recovery.constprop.0+0x82/0x180   Call Trace:    &amp;lt;TASK&amp;gt;    ? __die+0x20/0x70    ? page_fault_oops+0x75/0x170    ? exc_page_fault+0x64/0x140    ? asm_exc_page_fault+0x22/0x30    ? ublk_ctrl_start_recovery.constprop.0+0x82/0x180    ublk_ctrl_uring_cmd+0x4f7/0x6c0    ? pick_next_task_idle+0x26/0x40    io_uring_cmd+0x9a/0x1b0    io_issue_sqe+0x193/0x3f0    io_wq_submit_work+0x9b/0x390    io_worker_handle_work+0x165/0x360    io_wq_worker+0xcb/0x2f0    ? finish_task_switch.isra.0+0x203/0x290    ? finish_task_switch.isra.0+0x203/0x290    ? __pfx_io_wq_worker+0x10/0x10    ret_from_fork+0x2d/0x50    ? __pfx_io_wq_worker+0x10/0x10    ret_from_fork_asm+0x1a/0x30    &amp;lt;/TASK&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46735</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2173 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</guid>
    </item>
  </channel>
</rss>
