Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49542

5.5 · MEDIUM

In 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, th…

Published Feb 26, 2025CWE-667EPSS 0.20%

Overview

CVE-2022-49542 is a medium-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In 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().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/09c772557a4fd9490fed1bfb133268313ea22213Refgit.kernel.org/stable/c/271725e4028559ae7974d762a8467dc9de412f2eRefgit.kernel.org/stable/c/cc6501afccec55b8b6c90584cbf71f1fefa77d1eRefgit.kernel.org/stable/c/e294647b1aed4247fe52851f3a3b2b19ae906228

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49542?

CVE-2022-49542 is a medium-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-49542?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-49542?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49542?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49542 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999