CVE-2026-64475

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

vfio/pci: Release the VGA arbiter client on register_device() failure

The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration.

In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device.

Add the required VGA unwind callout.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 27, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e0a3f642e607848669235f5069f35640abbfc88
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d65decde9afd2bd78bcfffdc0df73b82a0b5509
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52adb2dff7ce3d8430e2bdc5988b618a430def85
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42d758a09d2c46c42357ecde9a5492f015bde2e5
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/278a5659c391fe5afe5f9ce1bad1fd24e90144f1
generic

vfio/pci: Release the VGA arbiter client on register_device() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f2a35a0c7ea7da347b814750eaa78adf3582381

Vendor Advisories for CVE-2026-64475(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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.

  1. 2026-07-27 05:26 UTCEG score recompute
  2. 2026-07-27 05:26 UTCGHSA enrichment
  3. 2026-07-27 05:13 UTCEG score recompute 8.80
  4. 2026-07-27 05:13 UTCGHSA enrichment
  5. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 02:46 UTCEG score recompute
  9. 2026-07-26 02:46 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 10:39 UTCNVD update
  13. 2026-07-25 09:26 UTCEG score recompute
  14. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64475?
CVE-2026-64475 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfiopcivga_init() as the last failure point of what is now vfiopcicoreregisterdevice() without introducing an…
When was CVE-2026-64475 disclosed?
CVE-2026-64475 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64475 actively exploited?
CVE-2026-64475 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 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64475?
CVE-2026-64475 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64475, 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

Explore the affected products and dependency analysis for CVE-2026-64475

Explore →

Is Your Infrastructure Affected by CVE-2026-64475?

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