| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49730: scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted |
| |
| A use-after-free crash can occur after an ELS LOGO is aborted. |
| |
| Specifically, a nodelist structure is freed and then |
| ndlp->vport->cfg_log_verbose is dereferenced in lpfc_nlp_get() when the |
| discovery state machine is mistakenly called a second time with |
| NLP_EVT_DEVICE_RM argument. |
| |
| Rework lpfc_cmpl_els_logo() to prevent the duplicate calls to release a |
| nodelist structure. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49730 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.15.49 with commit 5e83869e29448958f8ae2c6911f350318f75e4fc |
| Fixed in 5.18.6 with commit eea34ce23dc3a595695856dc73bb132a9c5a2902 |
| Fixed in 5.19 with commit b1b3440f437b75fb2a9b0cfe58df461e40eca474 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2022-49730 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/scsi/lpfc/lpfc_els.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/5e83869e29448958f8ae2c6911f350318f75e4fc |
| https://git.kernel.org/stable/c/eea34ce23dc3a595695856dc73bb132a9c5a2902 |
| https://git.kernel.org/stable/c/b1b3440f437b75fb2a9b0cfe58df461e40eca474 |
