CVE-2023-54108

scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests

N/A
Published: December 24, 2025 at 01:06 PM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.16.19v ≥ 5.17.25.10.110 ≤ v < 5.10.1735.15.33 ≤ v < 5.15.995.16.19 ≤ v < 5.175.17.2 ≤ v < 5.185.18 ≤ v < 6.1.165.18 ≤ v < 6.2.35.18 ≤ v < 6.35.4.189 ≤ v < 5.4.2352d087c7e55db420107c3ea97b228e067a7b488a15.10.1105.15.335.16.195.17.25.185.4.189910a791a6d7fd331f231f48200e18babb5197699765319079131d6a6019caec661825808c6405f1c05f4f6485726faae08073f947368ee10439d3f0c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523c9d6081a5f18286ad62afc1e9e06a90cfd626902
Vendor states this is fixed in 3a564de3a299856f2cbd289649cea2e20d671a43 (fixed)
Vendor states this is fixed in 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3 (fixed)
Vendor states this is fixed in 77302fb0e357da666d5249a6e91078feeef3dade (fixed)
Vendor states this is fixed in ad6af23593594402c826eefdf43ae174e5f0f202 (fixed)
Vendor states this is fixed in c75e6aef5039830cce5d4cf764dd204522f89e6b (fixed)
Vendor states this is fixed in e596253113b69b4018818260bd5da40c201bee73 (fixed)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.99 (unaffected)
Affected range stops below 5.17, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 5.4.235 (unaffected)
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card