LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel qla2xxx Fibre Channel driver issue involving duplicate DMA handling for NVMe link-service requests. The public record describes a debug-kernel warning and call trace, not confirmed data compromise, privilege escalation, or remote code execution.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency, unless critical storage infrastructure uses qla2xxx/NVMe-FC and is showing DMA warning instability. No active exploitation is supported by the supplied sources.

Technical view

In qla2xxx, NVMe LS request unmapping called DMA APIs even though the Fibre Channel layer already handled the mapping. The fix removes driver-level DMA mapping/unmapping for this path to prevent DMA-API map-check warnings in debug kernels.

Likely exposure

Exposure appears limited to Linux systems using the qla2xxx SCSI/Fibre Channel driver with NVMe over Fibre Channel paths. The source bundle lists Linux kernel versions and stable commits, but provides no CVSS, CWE, or product distribution advisories.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. Available evidence describes an internal kernel warning condition, not an attacker workflow.

Researcher notes

Evidence is narrow: the record describes a DMA-API call trace resolved by removing redundant mapping in qla2xxx. The bundle lacks CVSS, CWE, exploitability analysis, and downstream distro status, so impact assessment remains constrained.

Mitigation direction

  • Check the running kernel against vendor Linux advisories for CVE-2023-54108.
  • Apply the relevant Linux stable kernel update containing the qla2xxx fix.
  • Prioritize systems using QLogic qla2xxx Fibre Channel or NVMe over Fibre Channel.
  • If patching is delayed, monitor vendor guidance for supported mitigations.

Validation and detection

  • Inventory hosts with the qla2xxx kernel module loaded or packaged.
  • Confirm kernel version includes the referenced stable qla2xxx fix.
  • Review kernel logs for DMA-API warnings involving qla_nvme_ls_unmap.
  • Validate through distribution-specific security tooling where available.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54108 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2d087c7e55db420107c3ea97b228e067a7b488a1, 0910a791a6d7fd331f231f48200e18babb519769, c9d6081a5f18286ad62afc1e9e06a90cfd626902, c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523, c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523, c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523, 9765319079131d6a6019caec661825808c6405f1, c05f4f6485726faae08073f947368ee10439d3f0, 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2unaffected
LinuxLinux5.18, 0, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.