<?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>Sat, 03 Oct 2026 04:05:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02223</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02223</link>
      <description>bdu:2026-02223</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02223</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-310624</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310624</link>
      <description>EUVD-2026-310624</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310624</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49536</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49536</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock&lt;/p&gt;
&lt;p&gt;During stress I/O tests with 500+ vports, hard LOCKUP call traces are
observed.&lt;/p&gt;
&lt;p&gt;CPU A:
 native_queued_spin_lock_slowpath+0x192
 _raw_spin_lock_irqsave+0x32
 lpfc_handle_fcp_err+0x4c6
 lpfc_fcp_io_cmd_wqe_cmpl+0x964
 lpfc_sli4_fp_handle_cqe+0x266
 __lpfc_sli4_process_cq+0x105
 __lpfc_sli4_hba_process_cq+0x3c
 lpfc_cq_poll_hdler+0x16
 irq_poll_softirq+0x76
 __softirqentry_text_start+0xe4
 irq_exit+0xf7
 do_IRQ+0x7f&lt;/p&gt;
&lt;p&gt;CPU B:
 native_queued_spin_lock_slowpath+0x5b
 _raw_spin_lock+0x1c
 lpfc_abort_handler+0x13e
 scmd_eh_abort_handler+0x85
 process_one_work+0x1a7
 worker_thread+0x30
 kthread+0x112
 ret_from_fork+0x1f&lt;/p&gt;
&lt;p&gt;Diagram of lockup:&lt;/p&gt;
&lt;p&gt;CPUA                            CPUB
----                            ----
lpfc_cmd-&amp;gt;buf_lock
                            phba-&amp;gt;hbalock
                            lpfc_cmd-&amp;gt;buf_lock
phba-&amp;gt;hbalock&lt;/p&gt;
&lt;p&gt;Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in
lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock
first before phba-&amp;gt;hbalock.&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: lpfc: Fix SCSI I/O completion and abort handler deadlock&lt;/p&gt;
&lt;p&gt;During stress I/O tests with 500+ vports, hard LOCKUP call traces are
observed.&lt;/p&gt;
&lt;p&gt;CPU A:
 native_queued_spin_lock_slowpath+0x192
 _raw_spin_lock_irqsave+0x32
 lpfc_handle_fcp_err+0x4c6
 lpfc_fcp_io_cmd_wqe_cmpl+0x964
 lpfc_sli4_fp_handle_cqe+0x266
 __lpfc_sli4_process_cq+0x105
 __lpfc_sli4_hba_process_cq+0x3c
 lpfc_cq_poll_hdler+0x16
 irq_poll_softirq+0x76
 __softirqentry_text_start+0xe4
 irq_exit+0xf7
 do_IRQ+0x7f&lt;/p&gt;
&lt;p&gt;CPU B:
 native_queued_spin_lock_slowpath+0x5b
 _raw_spin_lock+0x1c
 lpfc_abort_handler+0x13e
 scmd_eh_abort_handler+0x85
 process_one_work+0x1a7
 worker_thread+0x30
 kthread+0x112
 ret_from_fork+0x1f&lt;/p&gt;
&lt;p&gt;Diagram of lockup:&lt;/p&gt;
&lt;p&gt;CPUA                            CPUB
----                            ----
lpfc_cmd-&amp;gt;buf_lock
                            phba-&amp;gt;hbalock
                            lpfc_cmd-&amp;gt;buf_lock
phba-&amp;gt;hbalock&lt;/p&gt;
&lt;p&gt;Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in
lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock
first before phba-&amp;gt;hbalock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49536</guid>
    </item>
    <item>
      <title>GHSA-wpwm-r528-7p8j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wpwm-r528-7p8j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock&lt;/p&gt;
&lt;p&gt;During stress I/O tests with 500+ vports, hard LOCKUP call traces are
observed.&lt;/p&gt;
&lt;p&gt;CPU A:
 native_queued_spin_lock_slowpath+0x192
 _raw_spin_lock_irqsave+0x32
 lpfc_handle_fcp_err+0x4c6
 lpfc_fcp_io_cmd_wqe_cmpl+0x964
 lpfc_sli4_fp_handle_cqe+0x266
 __lpfc_sli4_process_cq+0x105
 __lpfc_sli4_hba_process_cq+0x3c
 lpfc_cq_poll_hdler+0x16
 irq_poll_softirq+0x76
 __softirqentry_text_start+0xe4
 irq_exit+0xf7
 do_IRQ+0x7f&lt;/p&gt;
&lt;p&gt;CPU B:
 native_queued_spin_lock_slowpath+0x5b
 _raw_spin_lock+0x1c
 lpfc_abort_handler+0x13e
 scmd_eh_abort_handler+0x85
 process_one_work+0x1a7
 worker_thread+0x30
 kthread+0x112
 ret_from_fork+0x1f&lt;/p&gt;
&lt;p&gt;Diagram of lockup:&lt;/p&gt;
&lt;p&gt;CPUA                            CPUB
----                            ----
lpfc_cmd-&amp;gt;buf_lock
                            phba-&amp;gt;hbalock
                            lpfc_cmd-&amp;gt;buf_lock
phba-&amp;gt;hbalock&lt;/p&gt;
&lt;p&gt;Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in
lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock
first before phba-&amp;gt;hbalock.&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: lpfc: Fix SCSI I/O completion and abort handler deadlock&lt;/p&gt;
&lt;p&gt;During stress I/O tests with 500+ vports, hard LOCKUP call traces are
observed.&lt;/p&gt;
&lt;p&gt;CPU A:
 native_queued_spin_lock_slowpath+0x192
 _raw_spin_lock_irqsave+0x32
 lpfc_handle_fcp_err+0x4c6
 lpfc_fcp_io_cmd_wqe_cmpl+0x964
 lpfc_sli4_fp_handle_cqe+0x266
 __lpfc_sli4_process_cq+0x105
 __lpfc_sli4_hba_process_cq+0x3c
 lpfc_cq_poll_hdler+0x16
 irq_poll_softirq+0x76
 __softirqentry_text_start+0xe4
 irq_exit+0xf7
 do_IRQ+0x7f&lt;/p&gt;
&lt;p&gt;CPU B:
 native_queued_spin_lock_slowpath+0x5b
 _raw_spin_lock+0x1c
 lpfc_abort_handler+0x13e
 scmd_eh_abort_handler+0x85
 process_one_work+0x1a7
 worker_thread+0x30
 kthread+0x112
 ret_from_fork+0x1f&lt;/p&gt;
&lt;p&gt;Diagram of lockup:&lt;/p&gt;
&lt;p&gt;CPUA                            CPUB
----                            ----
lpfc_cmd-&amp;gt;buf_lock
                            phba-&amp;gt;hbalock
                            lpfc_cmd-&amp;gt;buf_lock
phba-&amp;gt;hbalock&lt;/p&gt;
&lt;p&gt;Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in
lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock
first before phba-&amp;gt;hbalock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wpwm-r528-7p8j</guid>
    </item>
    <item>
      <title>RHSA-2022:7683 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2022:7683</link>
      <description>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: race condition in VT_RESIZEX ioctl when vc_cons[i].d is already NULL leading to NULL pointer dereference kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: memory leak for large arguments in video_usercopy function in drivers/media/v4l2-core/v4l2-ioctl.c kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: NFSD: Fix READDIR buffer overflow kernel: cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: regmap: Fix possible double-free in regcache_rbtree_exit() kernel: ethtool: do not perform operations on net devices being unregistered kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: use-after-free in tc_new_tfilter() in net/sched/cls_api.c kernel: KVM: cm…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: off-path attacker may inject data or terminate victim&amp;#39;s TCP session kernel: race condition in VT_RESIZEX ioctl when vc_cons[i].d is already NULL leading to NULL pointer dereference kernel: use-after-free vulnerability in function sco_sock_sendmsg() kernel: memory leak for large arguments in video_usercopy function in drivers/media/v4l2-core/v4l2-ioctl.c kernel: veth: ensure skb entering GRO are not cloned. kernel: inet: fully convert sk-&amp;gt;sk_rx_dst to RCU rules kernel: NFSD: Fix READDIR buffer overflow kernel: cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free kernel: regmap: Fix possible double-free in regcache_rbtree_exit() kernel: ethtool: do not perform operations on net devices being unregistered kernel: scsi: scsi_debug: Fix type in min_t to avoid stack OOB kernel: KVM: x86/mmu: Zap _all_ roots when unmapping gfn range in TDP MMU kernel: udmabuf: validate ubuf-&amp;gt;pagecount kernel: drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() kernel: smb2_ioctl_query_info NULL pointer dereference kernel: NULL pointer dereference in udf_expand_file_adinicbdue() during writeback kernel: swiotlb information leak with DMA_FROM_DEVICE kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM kernel: race condition in snd_pcm_hw_free leading to use-after-free kernel: use-after-free in tc_new_tfilter() in net/sched/cls_api.c kernel: KVM: cm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2022:7683</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01600-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:01600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49536</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49536</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 145 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock During stress I/O tests with 500+ vports, hard LOCKUP call traces are observed. CPU A:  native_queued_spin_lock_slowpath+0x192  _raw_spin_lock_irqsave+0x32  lpfc_handle_fcp_err+0x4c6  lpfc_fcp_io_cmd_wqe_cmpl+0x964  lpfc_sli4_fp_handle_cqe+0x266  __lpfc_sli4_process_cq+0x105  __lpfc_sli4_hba_process_cq+0x3c  lpfc_cq_poll_hdler+0x16  irq_poll_softirq+0x76  __softirqentry_text_start+0xe4  irq_exit+0xf7  do_IRQ+0x7f CPU B:  native_queued_spin_lock_slowpath+0x5b  _raw_spin_lock+0x1c  lpfc_abort_handler+0x13e  scmd_eh_abort_handler+0x85  process_one_work+0x1a7  worker_thread+0x30  kthread+0x112  ret_from_fork+0x1f Diagram of lockup: CPUA                            CPUB ----                            ---- lpfc_cmd-&amp;gt;buf_lock                             phba-&amp;gt;hbalock                             lpfc_cmd-&amp;gt;buf_lock phba-&amp;gt;hbalock Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock first before phba-&amp;gt;hbalock.&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 145 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock During stress I/O tests with 500+ vports, hard LOCKUP call traces are observed. CPU A:  native_queued_spin_lock_slowpath+0x192  _raw_spin_lock_irqsave+0x32  lpfc_handle_fcp_err+0x4c6  lpfc_fcp_io_cmd_wqe_cmpl+0x964  lpfc_sli4_fp_handle_cqe+0x266  __lpfc_sli4_process_cq+0x105  __lpfc_sli4_hba_process_cq+0x3c  lpfc_cq_poll_hdler+0x16  irq_poll_softirq+0x76  __softirqentry_text_start+0xe4  irq_exit+0xf7  do_IRQ+0x7f CPU B:  native_queued_spin_lock_slowpath+0x5b  _raw_spin_lock+0x1c  lpfc_abort_handler+0x13e  scmd_eh_abort_handler+0x85  process_one_work+0x1a7  worker_thread+0x30  kthread+0x112  ret_from_fork+0x1f Diagram of lockup: CPUA                            CPUB ----                            ---- lpfc_cmd-&amp;gt;buf_lock                             phba-&amp;gt;hbalock                             lpfc_cmd-&amp;gt;buf_lock phba-&amp;gt;hbalock Fix by reordering the taking of the lpfc_cmd-&amp;gt;buf_lock and phba-&amp;gt;hbalock in lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&amp;gt;buf_lock first before phba-&amp;gt;hbalock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49536</guid>
    </item>
  </channel>
</rss>
