CVE-2022-49542

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg()<br /> <br /> In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard<br /> lockup call trace hangs the system.<br /> <br /> Call Trace:<br /> _raw_spin_lock_irqsave+0x32/0x40<br /> lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]<br /> lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]<br /> lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]<br /> lpfc_els_flush_cmd+0x43c/0x670 [lpfc]<br /> lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]<br /> lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]<br /> lpfc_do_work+0x1485/0x1d70 [lpfc]<br /> kthread+0x112/0x130<br /> ret_from_fork+0x1f/0x40<br /> Kernel panic - not syncing: Hard LOCKUP<br /> <br /> The same CPU tries to claim the phba-&gt;port_list_lock twice.<br /> <br /> Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and<br /> lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need<br /> to take the phba-&gt;port_list_lock within lpfc_dmp_dbg().