CVE-2023-54108: scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 3a564de3a299856f2cbd289649cea2e20d671a43, 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3, 5.10.173.
Low priority for now. Upgrade to Linux Linux 3a564de3a299856f2cbd289649cea2e20d671a43, 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3, 5.10.173 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9765319079131d6a6019caec661825808c6405f1, c05f4f6485726faae08073f947368ee10439d3f0, 5.18affected
- 2d087c7e55db420107c3ea97b228e067a7b488a1 and later · before 3a564de3a299856f2cbd289649cea2e20d671a43affected · git
- 0910a791a6d7fd331f231f48200e18babb519769 and later · before e596253113b69b4018818260bd5da40c201bee73affected · git
- c9d6081a5f18286ad62afc1e9e06a90cfd626902 and later · before 77302fb0e357da666d5249a6e91078feeef3dadeaffected · git
- c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and later · before 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3affected · git
- c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and later · before ad6af23593594402c826eefdf43ae174e5f0f202affected · git
- c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 and later · before c75e6aef5039830cce5d4cf764dd204522f89e6baffected · git
- 5.4.189 and later · before 5.4.235affected · semver
- 5.10.110 and later · before 5.10.173affected · semver
- 5.15.33 and later · before 5.15.99affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54105Dec 24, 2025 · can: isotp: check CAN address family in isotp_bind()0Monitor
- ← EarlierCVE-2023-54106Dec 24, 2025 · net/mlx5: fix potential memory leak in mlx5e_init_rep_rx0Monitor
- Later →CVE-2023-54109Dec 24, 2025 · media: rcar_fdp1: Fix refcount leak in probe and remove function0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a564de3a299856f2cbd289649cea2e20d671a43 | Vendor (CNA) |
| Linux Linux | 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3 | Vendor (CNA) |
| Linux Linux | 5.10.173 | Vendor (CNA) |
| Linux Linux | 5.15.99 | Vendor (CNA) |
| Linux Linux | 5.17 | Vendor (CNA) |
| Linux Linux | 5.18 | Vendor (CNA) |
| Linux Linux | 5.4.235 | Vendor (CNA) |
| Linux Linux | 77302fb0e357da666d5249a6e91078feeef3dade | Vendor (CNA) |
| Linux Linux | ad6af23593594402c826eefdf43ae174e5f0f202 | Vendor (CNA) |
| Linux Linux | c75e6aef5039830cce5d4cf764dd204522f89e6b | Vendor (CNA) |
| Linux Linux | e596253113b69b4018818260bd5da40c201bee73 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3ee4f1991c54c6707aa9df47e51c02ea25bb63e3
- git.kernel.org/stable/c/77302fb0e357da666d5249a6e91078feeef3dade
- git.kernel.org/stable/c/ad6af23593594402c826eefdf43ae174e5f0f202
- git.kernel.org/stable/c/c75e6aef5039830cce5d4cf764dd204522f89e6b
- git.kernel.org/stable/c/e596253113b69b4018818260bd5da40c201bee73
Vendor advisories and official records. Exploit/PoC links are deliberately left out.