CVE-2026-64254: Linux kernel · NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 8 Nov 2026, 16:35 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel to avoid calling pci_iounmap() with an offset when PEER_SPAD and CONFIG share a PCI BAR. Users should update to the fixed kernel version once available. No additional mitigation is indicated.
Description
A Linux kernel vulnerability was fixed in the NTB epf module where pci_iounmap() was called with an offset when PEER_SPAD and CONFIG shared a PCI BAR. This caused unnecessary unmapping attempts, triggering kernel warnings related to vunmap() of nonexistent vm areas during module teardown.
References
- git.kernel.org/stable/c/eb47b9bffd07a47b84910847cb5ea066ce184055 (opens in a new tab)
- git.kernel.org/stable/c/06f6dd2ff2bd07eaf7178a807407ff27e85122b4 (opens in a new tab)
- git.kernel.org/stable/c/a4be4a1308f02bff79a30eea2d04ead5b63685f2 (opens in a new tab)
- git.kernel.org/stable/c/81371dbd23601f67f01372817fdbab42c5601e43 (opens in a new tab)
- git.kernel.org/stable/c/9764a786ba98db58f0725913c369e721253aba33 (opens in a new tab)
- git.kernel.org/stable/c/d876153680e3d721d385e554def919bce3d18c74 (opens in a new tab)