Skip to main content
VulnerabilityPublished Updated

CVE-2026-64254: Linux kernel · NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 8 Nov 2026, 16:35 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Community reviews

Loading reviews…