CVE-2023-54108 — scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 2d087c7e55db420107c3ea97b228e067a7b488a1 and < 3a564de3a299856f2cbd289649cea2e20d671a43≥ 0910a791a6d7fd331f231f48200e18babb519769 and < e596253113b69b4018818260bd5da40c201bee73≥ c9d6081a5f18286ad62afc1e9e06a90cfd626902 and < 77302fb0e357da666d5249a6e91078feeef3dade≥ c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and < 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3≥ c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and < ad6af23593594402c826eefdf43ae174e5f0f202≥ c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and < c75e6aef5039830cce5d4cf764dd204522f89e6bversion 9765319079131d6a6019caec661825808c6405f1version c05f4f6485726faae08073f947368ee10439d3f0 and 6 more≥ 5.4.189 and < 5.4.235≥ 5.10.110 and < 5.10.173≥ 5.15.33 and < 5.15.99≥ 5.16.19 and < 5.17≥ 5.17.2 and < 5.18version 5.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- git.kernel.org/stable/c/ad6af23593594402c826eefdf43ae174e5f0f202
- git.kernel.org/stable/c/3a564de3a299856f2cbd289649cea2e20d671a43
- git.kernel.org/stable/c/c75e6aef5039830cce5d4cf764dd204522f89e6b
- git.kernel.org/stable/c/3ee4f1991c54c6707aa9df47e51c02ea25bb63e3
- git.kernel.org/stable/c/e596253113b69b4018818260bd5da40c201bee73
- git.kernel.org/stable/c/77302fb0e357da666d5249a6e91078feeef3dade
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 15h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 15h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-54108 is "scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.