CVE-2022-50027: scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE
In the Linux kernel, the following vulnerability has been resolved:
scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE
There is no corresponding free routine if lpfc_sli4_issue_wqe fails to
issue the CMF WQE in lpfc_issue_cmf_sync_wqe.
If ret_val is non-zero, then free the iocbq request structure.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50027 is a Linux kernel memory leak in the lpfc SCSI driver. If issuing a CMF work queue entry fails, an internal request structure may not be freed. The main business risk is gradual resource loss and possible service instability on affected storage-connected Linux systems.
Executive priority
Handle through normal kernel patch management, with higher priority for production storage hosts using lpfc. There is no sourced evidence of active exploitation, but kernel memory leaks can affect availability if the error path is repeatedly hit.
Technical view
The flaw is in lpfc_issue_cmf_sync_wqe. When lpfc_sli4_issue_wqe returns a non-zero failure, the iocbq request structure lacked a corresponding free path. Kernel stable commits add cleanup on this error path. No CVSS, CWE, or active exploitation evidence is provided in the source bundle.
Likely exposure
Exposure appears limited to Linux kernels with the affected lpfc driver code path. Systems not using lpfc are less likely to be practically exposed. The provided affected-version data is incomplete and should be verified against kernel or distribution advisories.
Exploitation context
The cited sources describe a memory leak, not code execution or privilege escalation. CISA KEV status is false in the provided data, and no cited source reports active exploitation. Practical impact likely depends on triggering repeated CMF WQE issuance failures.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits. The version data in the bundle is not sufficiently clear to define exact vulnerable ranges for all distributions. Validate against upstream commits and downstream vendor backports before making exposure claims.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported lpfc fixes.
Prioritize storage servers using the lpfc driver.
If patching is delayed, monitor kernel memory and storage driver errors.
Validation and detection
Inventory Linux hosts and kernel versions.
Identify systems loading or packaging the lpfc driver.
Compare installed kernel changelogs against the referenced stable commits.
Confirm vendor distribution kernels include the backported fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cve · low confidence lookup
CVE-2022-50027 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
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.
Jun 18, 2025, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.