| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53038: scsi: lpfc: Check kzalloc() in lpfc_sli4_cgn_params_read() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: lpfc: Check kzalloc() in lpfc_sli4_cgn_params_read() |
| |
| If kzalloc() fails in lpfc_sli4_cgn_params_read(), then we rely on |
| lpfc_read_object()'s routine to NULL check pdata. |
| |
| Currently, an early return error is thrown from lpfc_read_object() to |
| protect us from NULL ptr dereference, but the errno code is -ENODEV. |
| |
| Change the errno code to a more appropriate -ENOMEM. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53038 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.15.105 with commit 67b8343998b84418bc5b5206aa01fe9b461a80ef |
| Fixed in 6.1.22 with commit 4829a1e1171536978b240a1438789c2e4d5c9715 |
| Fixed in 6.2.9 with commit 908dd9a0853a88155a5a36018c7e2b32ccf20379 |
| Fixed in 6.3 with commit 312320b0e0ec21249a17645683fe5304d796aec1 |
| |
| 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-2023-53038 |
| 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_init.c |
| drivers/scsi/lpfc/lpfc_sli.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/67b8343998b84418bc5b5206aa01fe9b461a80ef |
| https://git.kernel.org/stable/c/4829a1e1171536978b240a1438789c2e4d5c9715 |
| https://git.kernel.org/stable/c/908dd9a0853a88155a5a36018c7e2b32ccf20379 |
| https://git.kernel.org/stable/c/312320b0e0ec21249a17645683fe5304d796aec1 |
