| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025122412-CVE-2023-54108-d5be@gregkh> Date: Wed, 24 Dec 2025 14:07:05 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-54108: scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests The following message and call trace was seen with debug kernels: DMA-API: qla2xxx 0000:41:00.0: device driver failed to check map error [device address=0x00000002a3ff38d8] [size=1024 bytes] [mapped as single] WARNING: CPU: 0 PID: 2930 at kernel/dma/debug.c:1017 check_unmap+0xf42/0x1990 Call Trace: debug_dma_unmap_page+0xc9/0x100 qla_nvme_ls_unmap+0x141/0x210 [qla2xxx] Remove DMA mapping from the driver altogether, as it is already done by FC layer. This prevents the warning. The Linux kernel CVE team has assigned CVE-2023-54108 to this issue. Affected and fixed versions =========================== Issue introduced in 5.4.189 with commit 2d087c7e55db420107c3ea97b228e067a7b488a1 and fixed in 5.4.235 with commit 3a564de3a299856f2cbd289649cea2e20d671a43 Issue introduced in 5.10.110 with commit 0910a791a6d7fd331f231f48200e18babb519769 and fixed in 5.10.173 with commit e596253113b69b4018818260bd5da40c201bee73 Issue introduced in 5.15.33 with commit c9d6081a5f18286ad62afc1e9e06a90cfd626902 and fixed in 5.15.99 with commit 77302fb0e357da666d5249a6e91078feeef3dade Issue introduced in 5.18 with commit c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and fixed in 6.1.16 with commit 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3 Issue introduced in 5.18 with commit c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and fixed in 6.2.3 with commit ad6af23593594402c826eefdf43ae174e5f0f202 Issue introduced in 5.18 with commit c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and fixed in 6.3 with commit c75e6aef5039830cce5d4cf764dd204522f89e6b Issue introduced in 5.16.19 with commit 9765319079131d6a6019caec661825808c6405f1 Issue introduced in 5.17.2 with commit c05f4f6485726faae08073f947368ee10439d3f0 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-54108 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/qla2xxx/qla_nvme.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/3a564de3a299856f2cbd289649cea2e20d671a43 https://git.kernel.org/stable/c/e596253113b69b4018818260bd5da40c201bee73 https://git.kernel.org/stable/c/77302fb0e357da666d5249a6e91078feeef3dade https://git.kernel.org/stable/c/3ee4f1991c54c6707aa9df47e51c02ea25bb63e3 https://git.kernel.org/stable/c/ad6af23593594402c826eefdf43ae174e5f0f202 https://git.kernel.org/stable/c/c75e6aef5039830cce5d4cf764dd204522f89e6b
Powered by blists - more mailing lists