CVE-2026-64254
NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR
Description
In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR When BAR_PEER_SPAD and BAR_CONFIG share one PCI BAR, the module teardown path ends up calling pci_iounmap() on the same iomem with some offset, which is unnecessary and triggers a kernel warning like the following: Trying to vunmap() nonexistent vm area (0000000069a5ffe8) WARNING: mm/vmalloc.c:3470 at vunmap+0x58/0x68, CPU#5: modprobe/2937 [...] Call trace: vunmap+0x58/0x68 (P) iounmap+0x34/0x48 pci_iounmap+0x2c/0x40 ntb_epf_pci_remove+0x44/0x80 [ntb_hw_epf] pci_device_remove+0x48/0xf8 device_remove+0x50/0x88 device_release_driver_internal+0x1c8/0x228 driver_detach+0x50/0xb0 bus_remove_driver+0x74/0x100 driver_unregister+0x34/0x68 pci_unregister_driver+0x34/0xa0 ntb_epf_pci_driver_exit+0x14/0xfe0 [ntb_hw_epf] [...] Fix it by unmapping only when PEER_SPAD and CONFIG use difference bars.
INFO
Published Date :
July 24, 2026, 4:16 p.m.
Last Modified :
July 24, 2026, 4:16 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64254
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest version.
- Apply the specific patch for NTB: EPF module.
- Ensure PEER_SPAD and CONFIG use different BARs if possible.
- Test the module teardown path after update.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64254.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64254 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64254
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64254 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64254 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': 'eb47b9bffd07a47b84910847cb5ea066ce184055', 'versionType': 'git'}, {'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': '06f6dd2ff2bd07eaf7178a807407ff27e85122b4', 'versionType': 'git'}, {'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': 'a4be4a1308f02bff79a30eea2d04ead5b63685f2', 'versionType': 'git'}, {'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': '81371dbd23601f67f01372817fdbab42c5601e43', 'versionType': 'git'}, {'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': '9764a786ba98db58f0725913c369e721253aba33', 'versionType': 'git'}, {'status': 'affected', 'version': 'e75d5ae8ab88b7ffb3d1d56124b003f3555f74b4', 'lessThan': 'd876153680e3d721d385e554def919bce3d18c74', 'versionType': 'git'}], 'programFiles': ['drivers/ntb/hw/epf/ntb_hw_epf.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.0'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.0', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.1.177', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.144', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.95', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.38', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.3', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/ntb/hw/epf/ntb_hw_epf.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR When BAR_PEER_SPAD and BAR_CONFIG share one PCI BAR, the module teardown path ends up calling pci_iounmap() on the same iomem with some offset, which is unnecessary and triggers a kernel warning like the following: Trying to vunmap() nonexistent vm area (0000000069a5ffe8) WARNING: mm/vmalloc.c:3470 at vunmap+0x58/0x68, CPU#5: modprobe/2937 [...] Call trace: vunmap+0x58/0x68 (P) iounmap+0x34/0x48 pci_iounmap+0x2c/0x40 ntb_epf_pci_remove+0x44/0x80 [ntb_hw_epf] pci_device_remove+0x48/0xf8 device_remove+0x50/0x88 device_release_driver_internal+0x1c8/0x228 driver_detach+0x50/0xb0 bus_remove_driver+0x74/0x100 driver_unregister+0x34/0x68 pci_unregister_driver+0x34/0xa0 ntb_epf_pci_driver_exit+0x14/0xfe0 [ntb_hw_epf] [...] Fix it by unmapping only when PEER_SPAD and CONFIG use difference bars. Added Reference https://git.kernel.org/stable/c/06f6dd2ff2bd07eaf7178a807407ff27e85122b4 Added Reference https://git.kernel.org/stable/c/81371dbd23601f67f01372817fdbab42c5601e43 Added Reference https://git.kernel.org/stable/c/9764a786ba98db58f0725913c369e721253aba33 Added Reference https://git.kernel.org/stable/c/a4be4a1308f02bff79a30eea2d04ead5b63685f2 Added Reference https://git.kernel.org/stable/c/d876153680e3d721d385e554def919bce3d18c74 Added Reference https://git.kernel.org/stable/c/eb47b9bffd07a47b84910847cb5ea066ce184055