Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2d087c7e55db420107c3ea97b228e067a7b488a1 – < 3a564de3a299856f2cbd289649cea2e20d671a43
    • affected 0910a791a6d7fd331f231f48200e18babb519769 – < e596253113b69b4018818260bd5da40c201bee73
    • affected c9d6081a5f18286ad62afc1e9e06a90cfd626902 – < 77302fb0e357da666d5249a6e91078feeef3dade
    • affected c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 – < 3ee4f1991c54c6707aa9df47e51c02ea25bb63e3
    • affected c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 – < ad6af23593594402c826eefdf43ae174e5f0f202
    • affected c85ab7d9e27a80e48d5b7d7fb2fe2b0fdb2de523 – < c75e6aef5039830cce5d4cf764dd204522f89e6b
    • affected 9765319079131d6a6019caec661825808c6405f1
    • affected c05f4f6485726faae08073f947368ee10439d3f0
    • affected 5.4.189 – < 5.4.235
    • affected 5.10.110 – < 5.10.173
    • affected 5.15.33 – < 5.15.99
    • affected 5.16.19 – < 5.17
    • affected 5.17.2 – < 5.18
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54108 badge
[![CVE-2023-54108](https://cveledger.app/badge/CVE-2023-54108.svg)](https://cveledger.app/cve/CVE-2023-54108)

Record last updated .