# CVE-2023-54108: scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests

> A missing DMA error check in the qla2xxx driver can cause kernel warnings and potential instability, requiring a patch for system administrators.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2023-54108, DEBIAN-CVE-2023-54108, GHSA-w45h-m4r8-m765, UBUNTU-CVE-2023-54108

## What is CVE-2023-54108?

CVE-2023-54108 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2023-54108?


## How do I fix CVE-2023-54108?

Apply the vendor's patch.

## Is CVE-2023-54108 being exploited?

There is no known exploitation of CVE-2023-54108 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54108 and fix it if it is affected.

What it is: CVE-2023-54108 is a denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54108 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54108/ (Markdown: https://insights.sbomify.com/CVE-2023-54108/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54108
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54108
- OSV: https://osv.dev/vulnerability/CVE-2023-54108

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54108/
Summaries are generated and may contain mistakes; the official description above is the record.