Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue in the lpfc Fibre Channel SCSI driver. Under heavy storage stress, lock ordering can deadlock kernel paths handling SCSI I/O completion and aborts, causing hard lockups. It does not affect confidentiality or integrity in the provided scoring.
Executive priority
Handle as a moderate-priority infrastructure stability fix. It is not described as remotely exploitable or data-stealing, but affected storage servers could hard-lock under demanding conditions. Patch during the next suitable maintenance window, sooner for critical Fibre Channel workloads.
Technical view
CVE-2022-49536 is a CWE-667 improper locking issue in lpfc. The fix reorders lpfc_cmd->buf_lock and phba->hbalock acquisition in lpfc_abort_handler to match completion handling and avoid a deadlock observed during stress I/O with 500+ vports.
Likely exposure
Exposure is most likely on Linux systems using the lpfc driver for Fibre Channel storage, especially high-vport or heavy SCSI I/O environments. The CVSS vector indicates local attack surface and low privileges, but exact affected builds depend on kernel version and distributor backports.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Evidence describes stress-test lockups rather than public exploitation. Treat this primarily as a local availability and storage resiliency risk until vendor or distro advisories say otherwise.
Researcher notes
The affected-version data in the bundle is limited and somewhat range-like, so distro-specific exposure requires vendor mapping. The clearest technical evidence is the kernel commit description: a lock inversion between completion and abort handler paths in lpfc under stress.
Mitigation direction
- Apply a vendor kernel update containing the referenced lpfc stable fixes.
- Prioritize systems using lpfc with high vport counts or heavy storage I/O.
- Check Linux distribution advisories for fixed backported kernel builds.
- Schedule reboots where required for the patched kernel to take effect.
- Monitor affected hosts for hard lockups until remediation is complete.
Validation and detection
- Inventory Linux hosts using the lpfc Fibre Channel driver.
- Compare running kernels against vendor fixed versions or referenced stable commits.
- Review kernel logs for lpfc, SCSI abort, or hard LOCKUP traces.
- Confirm the patched kernel is active after maintenance reboot.
- Regression test storage I/O and abort handling in staging where practical.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-49536 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/7625e81de2164a082810e1f27547d388406da610CVE reference, Linux
- https://git.kernel.org/stable/c/21c0d469349957b5dc811c41200a2a998996ca8dCVE reference, Linux
- https://git.kernel.org/stable/c/0c4eed901285b9cae36a622f32bea3e92490da6cCVE reference, Linux
- https://git.kernel.org/stable/c/03cbbd7c2f5ee288f648f4aeedc765a181188553CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.