Vulnerability · Published Feb 26, 2025 · Assigned by Linux
CVE-2022-49535scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI
High 8.8
In plain English
A high-severity use-after-free 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.4% (higher than 29% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI If lpfc_issue_els_flogi() fails and returns non-zero status, the node reference count is decremented to trigger the release of the nodelist structure. However, if there is a prior registration or dev-loss-evt work pending, the node may be released prematurely. When dev-loss-evt completes, the released node is referenced causing a use-after-free null pointer dereference. Similarly, when processing non-zero ELS PLOGI completion status in lpfc_cmpl_els_plogi(), the ndlp flags are checked for a transport registration before triggering node removal. If dev-loss-evt work is pending, the node may be released prematurely and a subsequent call to lpfc_dev_loss_tmo_handler() results in a use after free ndlp dereference. Add test for pending dev-loss before decrementing the node reference count for FLOGI, PLOGI, PRLI, and ADISC handling.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49535 |
| Debian:13 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49535 |
| Debian:14 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux | 5.15.0-144.157 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux | 5.15.0-144.157 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1088.95 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1088.95 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1094.103 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1094.103 | USN-7711-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1094.103.1 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1087.96 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1087.96 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1085.91 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1085.91 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1070.78 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1070.78 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1080.83 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1080.83 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1083.89 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1083.89 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1084.89 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1084.89 | USN-7654-4 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-144.157 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-144.157 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1082.83 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1082.83 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1041.41 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1041.41 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1030.30 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1030.30 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1085.91 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1085.91 | USN-7654-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1083.86 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1083.86 | USN-7686-1 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1052.56 | UBUNTU-CVE-2022-49535 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1052.56 | USN-7654-5 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 52edb2caf675684acf2140a125de4774c691fecd – before c7dc74ab7975c9b96284abfe4cca756d75fa460452edb2caf675684acf2140a125de4774c691fecd – before 10663ebec0ad5c78493a0dd34c9ee4d73d7ca0df52edb2caf675684acf2140a125de4774c691fecd – before 577a942df3de2666f6947bdd3a5c9e8d30073424 |
| Linux | Linux | 5.11 |
Weakness: CWE-416 · Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H