Service interruption via duplicate DMA unmapping
Published Dec 24, 2025 · Updated Dec 24, 2025
Improper DMA handling in Linux qla2xxx allows local users to interrupt service by issuing NVMe Link Service requests. The qla_nvme_ls_unmap function unmaps a DMA buffer that the Fibre Channel layer has already unmapped, causing the DMA API check to report an invalid unmap. Exposure requires the qla2xxx driver and NVMe Link Service path; the published assessment limits the consequence to availability.
Summary
What happened
Improper DMA handling in Linux qla2xxx allows local users to interrupt service by issuing NVMe Link Service requests. The qla_nvme_ls_unmap function unmaps a DMA buffer that the Fibre Channel layer has already unmapped, causing the DMA API check to report an invalid unmap. Exposure requires the qla2xxx driver and NVMe Link Service path; the published assessment limits the consequence to availability.
The record
- CVE
- CVE-2023-54108
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0910a791a6d7fd331f231f48200e18babb519769 <e596253113b69b4018818260bd5da40c201bee73
- Affected versionversion=2d087c7e55db420107c3ea97b228e067a7b488a1 <3a564de3a299856f2cbd289649cea2e20d671a43
- Affected versionversion=5.18
- Affected versionversion=9765319079131d6a6019caec661825808c6405f1
- Affected versionversion=c05f4f6485726faae08073f947368ee10439d3f0
- Affected versionversion=c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 <3ee4f1991c54c6707aa9df47e51c02ea25bb63e3
- Affected versionversion=c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 <ad6af23593594402c826eefdf43ae174e5f0f202
- Affected versionversion=c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 <c75e6aef5039830cce5d4cf764dd204522f89e6b
- Affected versionversion=c9d6081a5f18286ad62afc1e9e06a90cfd626902 <77302fb0e357da666d5249a6e91078feeef3dade
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo