<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T08:37:57.806627+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-49536</id>
    <title>CVE-2022-49536 — scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock</title>
    <updated>2026-09-30T08:37:57.808310+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock</p>
<p>During stress I/O tests with 500+ vports, hard LOCKUP call traces are
observed.</p>
<p>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</p>
<p>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</p>
<p>Diagram of lockup:</p>
<p>CPUA                            CPUB
----                            ----
lpfc_cmd-&gt;buf_lock
                            phba-&gt;hbalock
                            lpfc_cmd-&gt;buf_lock
phba-&gt;hbalock</p>
<p>Fix by reordering the taking of the lpfc_cmd-&gt;buf_lock and phba-&gt;hbalock in
lpfc_abort_handler routine so that it tries to take the lpfc_cmd-&gt;buf_lock
first before phba-&gt;hbalock.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49536"/>
  </entry>
</feed>
