CVE-2026-64020: nvme-pci: fix dma_vecs leak on p2p memory

From: Greg Kroah-Hartman <[email protected]>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

nvme-pci: fix dma_vecs leak on p2p memory

We don't unmap P2P memory, so we don't need to track it. The dma_vec
allocation was getting leaked on the completion.

The Linux kernel CVE team has assigned CVE-2026-64020 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.17 with commit b8b7570a7ec872f2a27b775c4f8710ca8a357adf and fixed in 7.0.11 with commit 24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd
	Issue introduced in 6.17 with commit b8b7570a7ec872f2a27b775c4f8710ca8a357adf and fixed in 7.1 with commit 85686c72966c5ee637893f124ddb31a1cace7bee

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-64020
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/nvme/host/pci.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/24ea0de233d9ebb5ebd6f6018eaf2084af25e3dd
	https://git.kernel.org/stable/c/85686c72966c5ee637893f124ddb31a1cace7bee