CVE-2026-64254

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb47b9bffd07a47b84910847cb5ea066ce184055
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d876153680e3d721d385e554def919bce3d18c74
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a4be4a1308f02bff79a30eea2d04ead5b63685f2
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9764a786ba98db58f0725913c369e721253aba33
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81371dbd23601f67f01372817fdbab42c5601e43
generic

NTB: epf: Avoid pci_iounmap() with offset when PEER_SPAD and CONFIG share BAR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06f6dd2ff2bd07eaf7178a807407ff27e85122b4

Vendor Advisories for CVE-2026-64254(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 08:39 UTCEG score recompute
  3. 2026-09-18 08:39 UTCVendor advisory
  4. 2026-09-18 08:39 UTCGHSA enrichment
  5. 2026-09-17 09:14 UTCEG score recompute
  6. 2026-09-17 09:14 UTCVendor advisory
  7. 2026-09-17 09:14 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 06:40 UTCEG score recompute
  10. 2026-09-16 06:40 UTCVendor advisory
  11. 2026-09-16 06:40 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-14 16:07 UTCEG score recompute
  14. 2026-09-14 16:07 UTCVendor advisory
  15. 2026-09-14 16:07 UTCGHSA enrichment
  16. 2026-09-13 15:26 UTCVendor advisory
  17. 2026-09-13 15:26 UTCGHSA enrichment
  18. 2026-09-12 15:58 UTCEG score recompute
  19. 2026-09-12 15:58 UTCVendor advisory
  20. 2026-09-12 15:58 UTCGHSA enrichment
  21. 2026-09-11 16:36 UTCEG score recompute
  22. 2026-09-11 16:36 UTCVendor advisory
  23. 2026-09-11 16:36 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 09:37 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 14:42 UTCEG score recompute
  2. 2026-09-10 14:42 UTCVendor advisory
  3. 2026-09-10 14:42 UTCGHSA enrichment
  4. 2026-09-09 08:47 UTCEG score recompute
  5. 2026-09-09 08:47 UTCVendor advisory
  6. 2026-09-09 08:46 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:24 UTCVendor advisory
  9. 2026-09-07 21:24 UTCGHSA enrichment
  10. 2026-09-06 18:45 UTCEG score recompute
  11. 2026-09-06 18:45 UTCGHSA enrichment
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 19:23 UTCEG score recompute
  14. 2026-09-05 19:23 UTCGHSA enrichment
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-04 12:51 UTCEG score recompute
  17. 2026-09-04 12:51 UTCGHSA enrichment
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 23:16 UTCEG score recompute
  21. 2026-09-01 23:16 UTCGHSA enrichment
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-30 23:39 UTCEG score recompute
  25. 2026-08-30 23:39 UTCGHSA enrichment
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 01:22 UTCEPSS rescore
  28. 2026-08-30 00:17 UTCEG score recompute
  29. 2026-08-30 00:17 UTCGHSA enrichment
  30. 2026-08-28 21:42 UTCEPSS rescore
  31. 2026-08-27 22:37 UTCEG score recompute
  32. 2026-08-27 22:37 UTCGHSA enrichment
  33. 2026-08-26 23:16 UTCEG score recompute
  34. 2026-08-26 23:16 UTCGHSA enrichment
  35. 2026-08-26 14:47 UTCEPSS rescore
  36. 2026-08-25 23:53 UTCGHSA enrichment
  37. 2026-08-25 00:31 UTCEG score recompute
  38. 2026-08-25 00:31 UTCGHSA enrichment
  39. 2026-08-24 01:10 UTCEG score recompute
  40. 2026-08-24 01:10 UTCGHSA enrichment
  41. 2026-08-23 01:48 UTCEG score recompute
  42. 2026-08-23 01:48 UTCGHSA enrichment
  43. 2026-08-23 00:19 UTCEPSS rescore
  44. 2026-08-22 02:26 UTCEG score recompute
  45. 2026-08-22 02:26 UTCGHSA enrichment
  46. 2026-08-21 23:49 UTCEPSS rescore
  47. 2026-08-21 02:55 UTCEG score recompute
  48. 2026-08-21 02:55 UTCGHSA enrichment
  49. 2026-08-20 22:55 UTCEPSS rescore
  50. 2026-08-20 03:31 UTCEG score recompute
  51. 2026-08-20 03:31 UTCGHSA enrichment
  52. 2026-08-19 17:04 UTCEPSS rescore
  53. 2026-08-19 04:09 UTCEG score recompute
  54. 2026-08-19 04:09 UTCGHSA enrichment
  55. 2026-08-18 13:48 UTCEPSS rescore
  56. 2026-08-18 04:43 UTCEG score recompute
  57. 2026-08-18 04:43 UTCGHSA enrichment
  58. 2026-08-17 13:47 UTCEPSS rescore
  59. 2026-08-17 05:22 UTCEG score recompute
  60. 2026-08-17 05:22 UTCGHSA enrichment
  61. 2026-08-16 14:56 UTCEPSS rescore
  62. 2026-08-16 13:25 UTCEG score recompute
  63. 2026-08-16 13:25 UTCGHSA enrichment
  64. 2026-08-15 14:03 UTCEG score recompute
  65. 2026-08-15 14:03 UTCGHSA enrichment
  66. 2026-08-15 01:30 UTCEPSS rescore
  67. 2026-08-14 14:41 UTCEG score recompute
  68. 2026-08-14 14:41 UTCGHSA enrichment
  69. 2026-08-13 22:00 UTCEPSS rescore
  70. 2026-08-13 15:19 UTCEG score recompute
  71. 2026-08-13 15:19 UTCGHSA enrichment
  72. 2026-08-12 15:55 UTCEG score recompute▲ 5.50
  73. 2026-08-12 15:55 UTCGHSA enrichment
  74. 2026-08-12 15:55 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  75. 2026-08-12 13:51 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-64254?
CVE-2026-64254 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: NTB: epf: Avoid pciiounmap() with offset when PEERSPAD and CONFIG share BAR When BARPEERSPAD 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…
When was CVE-2026-64254 disclosed?
CVE-2026-64254 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64254 actively exploited?
CVE-2026-64254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64254?
CVE-2026-64254 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64254?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64254, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64254

Explore →

Is Your Infrastructure Affected by CVE-2026-64254?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs