LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50827: scsi: lpfc: Fix memory leak in lpfc_create_port()

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix memory leak in lpfc_create_port() Commit 5e633302ace1 ("scsi: lpfc: vmid: Add support for VMID in mailbox command") introduced allocations for the VMID resources in lpfc_create_port() after the call to scsi_host_alloc(). Upon failure on the VMID allocations, the new code would branch to the 'out' label, which returns NULL without unwinding anything, thus skipping the call to scsi_host_put(). Fix the problem by creating a separate label 'out_free_vmid' to unwind the VMID resources and make the 'out_put_shost' label call only scsi_host_put(), as was done before the introduction of allocations for VMID.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50827 is a Linux kernel memory leak in the lpfc SCSI driver. If VMID resource allocation fails during port creation, cleanup can be skipped. This is not listed as actively exploited, and the source bundle provides no CVSS score.

Executive priority

Treat as a targeted kernel maintenance issue, not an emergency. Prioritize storage infrastructure and systems using lpfc, then remediate through normal kernel update processes unless vendor guidance raises severity.

Technical view

A change adding VMID mailbox support introduced allocations in lpfc_create_port() after scsi_host_alloc(). On VMID allocation failure, the code returned through the wrong cleanup path, skipping scsi_host_put(). Stable kernel commits add separate unwind labels to free VMID resources and release the SCSI host correctly.

Likely exposure

Exposure is most likely on Linux systems running affected kernels where the lpfc driver code is present and used. The provided data lists Linux 5.14 and affected ranges through fixes associated with 5.15.76, 6.0.6, and 6.1, but distro kernel backports require vendor verification.

Exploitation context

The cited sources describe a memory leak triggered by an allocation-failure path. They do not describe remote exploitation, privilege requirements, proof-of-concept code, or active exploitation. KEV status is false in the provided bundle.

Researcher notes

Evidence is limited to the kernel fix description and stable commit references. No CVSS, CWE, exploitability analysis, or KEV listing is provided. Validation should focus on kernel lineage, lpfc usage, and whether the cleanup-path fix is present.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check your Linux distributor’s advisory for backported fixes and package versions.
  • Prioritize review of systems using the lpfc SCSI driver.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check whether the lpfc driver is present or loaded on storage-connected systems.
  • Confirm the kernel includes one of the referenced stable fixes or a vendor backport.
  • Track vendor advisories if using distribution-maintained kernels.
Prepared
Confidence
medium
Sources
5

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-50827 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

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.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5e633302ace1f61f8ea5a3ce21e19a4d79126cca, 5e633302ace1f61f8ea5a3ce21e19a4d79126cca, 5e633302ace1f61f8ea5a3ce21e19a4d79126ccaunaffected
LinuxLinux5.14, 0, 5.15.76, 6.0.6, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.