Vulnerability · Published Jun 18, 2025 · Assigned by Linux
CVE-2022-50027scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 91.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.0.2-1 | DEBIAN-CVE-2022-50027 |
| Debian:13 | linux | 6.0.2-1 | DEBIAN-CVE-2022-50027 |
| Debian:14 | linux | 6.0.2-1 | DEBIAN-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux | 5.15.0-53.59 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1023.27 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1023.29 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1024.30.1 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1022.29 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1020.25 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1008.12 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1018.21 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1018.23 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1021.26 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-53.59 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1015.15 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1022.28 | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1018.20 | UBUNTU-CVE-2022-50027 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-50027 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-50027 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | daebf93fc3a5d12b3bc928aebb168c68e754dda2 – before 9c8e2e607270a368834a0ef72aa82d970f89c596daebf93fc3a5d12b3bc928aebb168c68e754dda2 – before 4eb7a1beff03836d3df271cd23b790884e3facb9daebf93fc3a5d12b3bc928aebb168c68e754dda2 – before 2f67dc7970bce3529edce93a0a14234d88b3fcd5 |
| Linux | Linux | 5.15 |