CVE-2026-23174
published 2026-02-14CVE-2026-23174: In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_needs_unmap…
PriorityP420medium5.3
EPSS
0.15%
5.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_needs_unmap may be false, but change to true
while mapping the data iterator. Enabling swiotlb is one such case that
can change the result. The nvme driver needs to save the mapped dma
vectors to be unmapped later, so allocate as needed during iteration
rather than assume it was always allocated at the beginning. This fixes
a NULL dereference from accessing an uninitialized dma_vecs when the
device dma unmapping requirements change mid-iteration.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.18.10-1 (forky) | linux 6.18.10-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= b8b7570a7ec872f2a27b775c4f8710ca8a357adf < f3ed399e9aa6f36e92d2d0fe88b387915e9705fe | f3ed399e9aa6f36e92d2d0fe88b387915e9705fe |
| linux | linux | >= b8b7570a7ec872f2a27b775c4f8710ca8a357adf < 071be3b0b6575d45be9df9c5b612f5882bfc5e88 | 071be3b0b6575d45be9df9c5b612f5882bfc5e88 |
| linux | linux_kernel | >= 0 < 6.18.10-1 | 6.18.10-1 |
| linux | linux_kernel | >= 6.17.0 < 6.18.10 | 6.18.10 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: nvme-pci: handle changing device dma map requirements
vendor_redhat·2026-02-14
CVE-2026-23174 kernel: nvme-pci: handle changing device dma map requirements
kernel: nvme-pci: handle changing device dma map requirements
In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_needs_unmap may be false, but change to true
while mapping the data iterator. Enabling swiotlb is one such case that
can change the result. The nvme driver needs to save the mapped dma
vectors to be unmapped later, so allocate as needed during iteration
rather than assume it was always allocated at the beginning. This fixes
a NULL dereference from accessing an uninitialized dma_vecs when the
device dma unmapping requirements change mid-iteration.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel
Debian
CVE-2026-23174: linux - In the Linux kernel, the following vulnerability has been resolved: nvme-pci: h...
vendor_debian·2026
CVE-2026-23174 [LOW] CVE-2026-23174: linux - In the Linux kernel, the following vulnerability has been resolved: nvme-pci: h...
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_needs_unmap may be false, but change to true while mapping the data iterator. Enabling swiotlb is one such case that can change the result. The nvme driver needs to save the mapped dma vectors to be unmapped later, so allocate as needed during iteration rather than assume it was always allocated at the beginning. This fixes a NULL dereference from accessing an uninitialized dma_vecs when the device dma unmapping requirements change mid-iteration.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved (fixed in 6.18.10-1)
sid: resolved (fixed in 6.18.10-1)
trixie: resolved
VulDB
Linux Kernel up to 6.18.9 Nvme Driver dma_needs_unmap uninitialized pointer (Nessus ID 299098 / WID-SEC-2026-0421)
vuldb·2026-04-13
CVE-2026-23174 [CRITICAL] Linux Kernel up to 6.18.9 Nvme Driver dma_needs_unmap uninitialized pointer (Nessus ID 299098 / WID-SEC-2026-0421)
A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.18.9. This affects the function dma_needs_unmap of the component Nvme Driver. The manipulation results in uninitialized pointer.
This vulnerability was named CVE-2026-23174. The attack needs to be approached within the local network. There is no available exploit.
You should upgrade the affected component.
OSV
CVE-2026-23174: In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_nee
osv·2026-02-14
CVE-2026-23174 CVE-2026-23174: In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_nee
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_needs_unmap may be false, but change to true while mapping the data iterator. Enabling swiotlb is one such case that can change the result. The nvme driver needs to save the mapped dma vectors to be unmapped later, so allocate as needed during iteration rather than assume it was always allocated at the beginning. This fixes a NULL dereference from accessing an uninitialized dma_vecs when the device dma unmapping requirements change mid-iteration.
OSV
nvme-pci: handle changing device dma map requirements
osv·2026-02-14
CVE-2026-23174 nvme-pci: handle changing device dma map requirements
nvme-pci: handle changing device dma map requirements
In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_needs_unmap may be false, but change to true
while mapping the data iterator. Enabling swiotlb is one such case that
can change the result. The nvme driver needs to save the mapped dma
vectors to be unmapped later, so allocate as needed during iteration
rather than assume it was always allocated at the beginning. This fixes
a NULL dereference from accessing an uninitialized dma_vecs when the
device dma unmapping requirements change mid-iteration.
GHSA
GHSA-wrw7-63r4-jj3j: In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_n
ghsa_unreviewed·2026-02-14
CVE-2026-23174 GHSA-wrw7-63r4-jj3j: In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_n
In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: handle changing device dma map requirements
The initial state of dma_needs_unmap may be false, but change to true
while mapping the data iterator. Enabling swiotlb is one such case that
can change the result. The nvme driver needs to save the mapped dma
vectors to be unmapped later, so allocate as needed during iteration
rather than assume it was always allocated at the beginning. This fixes
a NULL dereference from accessing an uninitialized dma_vecs when the
device dma unmapping requirements change mid-iteration.
No detection rules found.
No public exploits indexed.
2026-02-14
Published