CVE-2022-50827
Last modified
CVE-2022-50827 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 5e633302ace1f61f8ea5a3ce21e19a4d79126cca, < 9749595feb33a1a2b848800192224ffeed5346b4; >= 5e633302ace1f61f8ea5a3ce21e19a4d79126cca, < 5ea1f195f51c2bb5915ccfb2b2885ca81ce9262b; >= 5e633302ace1f61f8ea5a3ce21e19a4d79126cca, < dc8e483f684a24cc06e1d5fa958b54db58855093 |
| Linux | Linux | 5.14 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2022-50827?
How severe is CVE-2022-50827?
How do I fix CVE-2022-50827?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50821In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50822In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50823In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50824In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50825In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50826In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50828In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50829In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50830In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50831Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-50832In the Linux kernel, the following vulnerability has been re…
- CVE-2022-50833In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2022-50827?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
