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

> A memory leak in the Linux kernel lpfc driver allows local attackers to cause a denial of service by exhausting system memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50827, GHSA-6pw2-377m-5mj9, UBUNTU-CVE-2022-50827

## What is CVE-2022-50827?

CVE-2022-50827 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2022-50827?


## How do I fix CVE-2022-50827?

Apply the vendor's patch.

## Is CVE-2022-50827 being exploited?

There is no known exploitation of CVE-2022-50827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50827 and fix it if it is affected.

What it is: CVE-2022-50827 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50827 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50827/ (Markdown: https://insights.sbomify.com/CVE-2022-50827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50827
- OSV: https://osv.dev/vulnerability/CVE-2022-50827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50827/
Summaries are generated and may contain mistakes; the official description above is the record.