<?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:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-05358</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-05358</link>
      <description>bdu:2025-05358</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-05358</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53041</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53041</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53041</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0509 — 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-2025-avi-0509</link>
      <description>certfr-2025-avi-0509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0509</guid>
    </item>
    <item>
      <title>EUVD-2026-320448</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320448</link>
      <description>EUVD-2026-320448</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320448</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53041</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53041</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Perform lockless command completion in abort path&lt;/p&gt;
&lt;p&gt;While adding and removing the controller, the following call trace was
observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50
CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1
RIP: 0010:dma_free_attrs+0x33/0x50&lt;/p&gt;
&lt;p&gt;Call Trace:
   qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]
   qla2x00_abort_srb+0x8e/0x250 [qla2xxx]
   ? ql_dbg+0x70/0x100 [qla2xxx]
   __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]
   qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]
   qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]
   qla2x00_remove_one+0x364/0x400 [qla2xxx]
   pci_device_remove+0x36/0xa0
   __device_release_driver+0x17a/0x230
   device_release_driver+0x24/0x30
   pci_stop_bus_device+0x68/0x90
   pci_stop_and_remove_bus_device_locked+0x16/0x30
   remove_store+0x75/0x90
   kernfs_fop_write_iter+0x11c/0x1b0
   new_sync_write+0x11f/0x1b0
   vfs_write+0x1eb/0x280
   ksys_write+0x5f/0xe0
   do_syscall_64+0x5c/0x80
   ? do_user_addr_fault+0x1d8/0x680
   ? do_syscall_64+0x69/0x80
   ? exc_page_fault+0x62/0x140
   ? asm_exc_page_fault+0x8/0x30
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The command was completed in the abort path during driver unload with a
lock held, causing the warning in abort path. Hence complete the command
without any lock held.&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;scsi: qla2xxx: Perform lockless command completion in abort path&lt;/p&gt;
&lt;p&gt;While adding and removing the controller, the following call trace was
observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50
CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1
RIP: 0010:dma_free_attrs+0x33/0x50&lt;/p&gt;
&lt;p&gt;Call Trace:
   qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]
   qla2x00_abort_srb+0x8e/0x250 [qla2xxx]
   ? ql_dbg+0x70/0x100 [qla2xxx]
   __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]
   qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]
   qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]
   qla2x00_remove_one+0x364/0x400 [qla2xxx]
   pci_device_remove+0x36/0xa0
   __device_release_driver+0x17a/0x230
   device_release_driver+0x24/0x30
   pci_stop_bus_device+0x68/0x90
   pci_stop_and_remove_bus_device_locked+0x16/0x30
   remove_store+0x75/0x90
   kernfs_fop_write_iter+0x11c/0x1b0
   new_sync_write+0x11f/0x1b0
   vfs_write+0x1eb/0x280
   ksys_write+0x5f/0xe0
   do_syscall_64+0x5c/0x80
   ? do_user_addr_fault+0x1d8/0x680
   ? do_syscall_64+0x69/0x80
   ? exc_page_fault+0x62/0x140
   ? asm_exc_page_fault+0x8/0x30
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The command was completed in the abort path during driver unload with a
lock held, causing the warning in abort path. Hence complete the command
without any lock held.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53041</guid>
    </item>
    <item>
      <title>GHSA-8vg7-5r5j-h4jq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8vg7-5r5j-h4jq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Perform lockless command completion in abort path&lt;/p&gt;
&lt;p&gt;While adding and removing the controller, the following call trace was
observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50
CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1
RIP: 0010:dma_free_attrs+0x33/0x50&lt;/p&gt;
&lt;p&gt;Call Trace:
   qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]
   qla2x00_abort_srb+0x8e/0x250 [qla2xxx]
   ? ql_dbg+0x70/0x100 [qla2xxx]
   __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]
   qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]
   qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]
   qla2x00_remove_one+0x364/0x400 [qla2xxx]
   pci_device_remove+0x36/0xa0
   __device_release_driver+0x17a/0x230
   device_release_driver+0x24/0x30
   pci_stop_bus_device+0x68/0x90
   pci_stop_and_remove_bus_device_locked+0x16/0x30
   remove_store+0x75/0x90
   kernfs_fop_write_iter+0x11c/0x1b0
   new_sync_write+0x11f/0x1b0
   vfs_write+0x1eb/0x280
   ksys_write+0x5f/0xe0
   do_syscall_64+0x5c/0x80
   ? do_user_addr_fault+0x1d8/0x680
   ? do_syscall_64+0x69/0x80
   ? exc_page_fault+0x62/0x140
   ? asm_exc_page_fault+0x8/0x30
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The command was completed in the abort path during driver unload with a
lock held, causing the warning in abort path. Hence complete the command
without any lock held.&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;scsi: qla2xxx: Perform lockless command completion in abort path&lt;/p&gt;
&lt;p&gt;While adding and removing the controller, the following call trace was
observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50
CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1
RIP: 0010:dma_free_attrs+0x33/0x50&lt;/p&gt;
&lt;p&gt;Call Trace:
   qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]
   qla2x00_abort_srb+0x8e/0x250 [qla2xxx]
   ? ql_dbg+0x70/0x100 [qla2xxx]
   __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]
   qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]
   qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]
   qla2x00_remove_one+0x364/0x400 [qla2xxx]
   pci_device_remove+0x36/0xa0
   __device_release_driver+0x17a/0x230
   device_release_driver+0x24/0x30
   pci_stop_bus_device+0x68/0x90
   pci_stop_and_remove_bus_device_locked+0x16/0x30
   remove_store+0x75/0x90
   kernfs_fop_write_iter+0x11c/0x1b0
   new_sync_write+0x11f/0x1b0
   vfs_write+0x1eb/0x280
   ksys_write+0x5f/0xe0
   do_syscall_64+0x5c/0x80
   ? do_user_addr_fault+0x1d8/0x680
   ? do_syscall_64+0x69/0x80
   ? exc_page_fault+0x62/0x140
   ? asm_exc_page_fault+0x8/0x30
   entry_SYSCALL_64_after_hwframe+0x44/0xae&lt;/p&gt;
&lt;p&gt;The command was completed in the abort path during driver unload with a
lock held, causing the warning in abort path. Hence complete the command
without any lock held.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8vg7-5r5j-h4jq</guid>
    </item>
    <item>
      <title>OESA-2025-2885 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2885</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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:scsi: pm8001: Fix tag leaks on errorIn pm8001_chip_set_dev_state_req(), pm8001_chip_fw_flash_update_req(),pm80xx_chip_phy_ctl_req() and pm8001_chip_reg_dev_req() add missing callsto pm8001_tag_free() to free the allocated tag when pm8001_mpi_build_cmd()fails.Similarly, in pm8001_exec_internal_task_abort(), if the chip -&amp;amp;gt;task_abortmethod fails, the tag allocated for the abort request task must befreed. Add the missing call to pm8001_tag_free().(CVE-2022-49121)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:scsi: qla2xxx: Fix scheduling while atomicThe driver makes a call into midlayer (fc_remote_port_delete) which can putthe thread to sleep. The thread that originates the call is in interruptcontext. The combination of the two trigger a crash. Schedule the call innon-interrupt context where it is more safe.kernel: BUG: scheduling while atomic: swapper/7/0/0x00010000kernel: Call Trace:kernel:  &amp;amp;lt;IRQ&amp;amp;gt;kernel:  dump_stack+0x66/0x81kernel:  __schedule_bug.cold.90+0x5/0x1dkernel:  __schedule+0x7af/0x960kernel:  schedule+0x28/0x80kernel:  schedule_timeout+0x26d/0x3b0kernel:  wait_for_completion+0xb4/0x140kernel:  ? wake_up_q+0x70/0x70kernel:  __wait_rcu_gp+0x12c/0x160kernel:  ? sdev_evt_alloc+0xc0/0x180 [scsi_mod]kernel:  synchronize_sched+0x6c/0x80kernel:  ? call_rcu_bh+0x20/0x20kernel:  ? __bpf_trace_rcu_invoke_ca…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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:scsi: pm8001: Fix tag leaks on errorIn pm8001_chip_set_dev_state_req(), pm8001_chip_fw_flash_update_req(),pm80xx_chip_phy_ctl_req() and pm8001_chip_reg_dev_req() add missing callsto pm8001_tag_free() to free the allocated tag when pm8001_mpi_build_cmd()fails.Similarly, in pm8001_exec_internal_task_abort(), if the chip -&amp;amp;gt;task_abortmethod fails, the tag allocated for the abort request task must befreed. Add the missing call to pm8001_tag_free().(CVE-2022-49121)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:scsi: qla2xxx: Fix scheduling while atomicThe driver makes a call into midlayer (fc_remote_port_delete) which can putthe thread to sleep. The thread that originates the call is in interruptcontext. The combination of the two trigger a crash. Schedule the call innon-interrupt context where it is more safe.kernel: BUG: scheduling while atomic: swapper/7/0/0x00010000kernel: Call Trace:kernel:  &amp;amp;lt;IRQ&amp;amp;gt;kernel:  dump_stack+0x66/0x81kernel:  __schedule_bug.cold.90+0x5/0x1dkernel:  __schedule+0x7af/0x960kernel:  schedule+0x28/0x80kernel:  schedule_timeout+0x26d/0x3b0kernel:  wait_for_completion+0xb4/0x140kernel:  ? wake_up_q+0x70/0x70kernel:  __wait_rcu_gp+0x12c/0x160kernel:  ? sdev_evt_alloc+0xc0/0x180 [scsi_mod]kernel:  synchronize_sched+0x6c/0x80kernel:  ? call_rcu_bh+0x20/0x20kernel:  ? __bpf_trace_rcu_invoke_ca…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2885</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01918-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01918-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-2025:01918-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53041</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53041</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Perform lockless command completion in abort path While adding and removing the controller, the following call trace was observed: WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50 CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1 RIP: 0010:dma_free_attrs+0x33/0x50 Call Trace:    qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]    qla2x00_abort_srb+0x8e/0x250 [qla2xxx]    ? ql_dbg+0x70/0x100 [qla2xxx]    __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]    qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]    qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]    qla2x00_remove_one+0x364/0x400 [qla2xxx]    pci_device_remove+0x36/0xa0    __device_release_driver+0x17a/0x230    device_release_driver+0x24/0x30    pci_stop_bus_device+0x68/0x90    pci_stop_and_remove_bus_device_locked+0x16/0x30    remove_store+0x75/0x90    kernfs_fop_write_iter+0x11c/0x1b0    new_sync_write+0x11f/0x1b0    vfs_write+0x1eb/0x280    ksys_write+0x5f/0xe0    do_syscall_64+0x5c/0x80    ? do_user_addr_fault+0x1d8/0x680    ? do_syscall_64+0x69/0x80    ? exc_page_fault+0x62/0x140    ? asm_exc_page_fault+0x8/0x30    entry_SYSCALL_64_after_hwframe+0x44/0xae The command was completed in the abort path during driver unload with a lock held, causing the warning in abort path. Hence complete the command without any lock held.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Perform lockless command completion in abort path While adding and removing the controller, the following call trace was observed: WARNING: CPU: 3 PID: 623596 at kernel/dma/mapping.c:532 dma_free_attrs+0x33/0x50 CPU: 3 PID: 623596 Comm: sh Kdump: loaded Not tainted 5.14.0-96.el9.x86_64 #1 RIP: 0010:dma_free_attrs+0x33/0x50 Call Trace:    qla2x00_async_sns_sp_done+0x107/0x1b0 [qla2xxx]    qla2x00_abort_srb+0x8e/0x250 [qla2xxx]    ? ql_dbg+0x70/0x100 [qla2xxx]    __qla2x00_abort_all_cmds+0x108/0x190 [qla2xxx]    qla2x00_abort_all_cmds+0x24/0x70 [qla2xxx]    qla2x00_abort_isp_cleanup+0x305/0x3e0 [qla2xxx]    qla2x00_remove_one+0x364/0x400 [qla2xxx]    pci_device_remove+0x36/0xa0    __device_release_driver+0x17a/0x230    device_release_driver+0x24/0x30    pci_stop_bus_device+0x68/0x90    pci_stop_and_remove_bus_device_locked+0x16/0x30    remove_store+0x75/0x90    kernfs_fop_write_iter+0x11c/0x1b0    new_sync_write+0x11f/0x1b0    vfs_write+0x1eb/0x280    ksys_write+0x5f/0xe0    do_syscall_64+0x5c/0x80    ? do_user_addr_fault+0x1d8/0x680    ? do_syscall_64+0x69/0x80    ? exc_page_fault+0x62/0x140    ? asm_exc_page_fault+0x8/0x30    entry_SYSCALL_64_after_hwframe+0x44/0xae The command was completed in the abort path during driver unload with a lock held, causing the warning in abort path. Hence complete the command without any lock held.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53041</guid>
    </item>
  </channel>
</rss>
