CVE-2026-64254 Details
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.
A vulnerability exists in the Linux kernel's NTB EPF driver related to improper handling of PCI I/O unmapping. When the PEER_SPAD and CONFIG bars share the same PCI base address, the driver incorrectly calls pci_iounmap() on the same I/O memory with an offset during the module teardown process. This unnecessary action triggers a kernel warning about unmapping a nonexistent virtual memory area. The issue arises because the driver does not properly differentiate between the memory bar mappings for PEER_SPAD and CONFIG, leading to the incorrect unmap operation.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/06f6dd2ff2bd07eaf7178a807407ff27e85122b4 | kernel.org | Patch |
| https://git.kernel.org/stable/c/81371dbd23601f67f01372817fdbab42c5601e43 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9764a786ba98db58f0725913c369e721253aba33 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a4be4a1308f02bff79a30eea2d04ead5b63685f2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d876153680e3d721d385e554def919bce3d18c74 | kernel.org | Patch |
| https://git.kernel.org/stable/c/eb47b9bffd07a47b84910847cb5ea066ce184055 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-617 | Reachable Assertion | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.0, < 6.1.177 >= 6.2, < 6.6.144 >= 6.7, < 6.12.95 >= 6.13, < 6.18.38 >= 6.19, < 7.1.3 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 17, 2026 | CVE Modified | kernel.org |
| Aug 12, 2026 | Initial Analysis | [email protected] |
| Jul 24, 2026 | New CVE Received | kernel.org |