n the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() In an attempt to log message 0126 with LOG_TRACE_EVENT, the following hard lockup call trace hangs the system. Call Trace: _raw_spin_lock_irqsave+0x32/0x40 lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] lpfc_do_work+0x1485/0x1d70 [lpfc] kthread+0x112/0x130 ret_from_fork+0x1f/0x40 Kernel panic - not syncing: Hard LOCKUP The same CPU tries to claim the phba->port_list_lock twice. Move the cfg_log_verbose checks as part of the lpfc_printf_vlog() and lpfc_printf_log() macros before calling lpfc_dmp_dbg(). There is no need to take the phba->port_list_lock within lpfc_dmp_dbg().
Configuration 1 (hide)
|
10 Mar 2025, 21:31
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Linux
Linux linux Kernel |
|
| CWE | CWE-667 | |
| References | () https://git.kernel.org/stable/c/09c772557a4fd9490fed1bfb133268313ea22213 - Patch | |
| References | () https://git.kernel.org/stable/c/271725e4028559ae7974d762a8467dc9de412f2e - Patch | |
| References | () https://git.kernel.org/stable/c/cc6501afccec55b8b6c90584cbf71f1fefa77d1e - Patch | |
| References | () https://git.kernel.org/stable/c/e294647b1aed4247fe52851f3a3b2b19ae906228 - Patch | |
| Summary |
|
|
| CPE | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
26 Feb 2025, 07:01
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2025-02-26 07:01
Updated : 2025-10-01 20:16
NVD link : CVE-2022-49542
Mitre link : CVE-2022-49542
CVE.ORG link : CVE-2022-49542
JSON object : View
Improper Locking