CVE-2026-64475
vfio/pci: Release the VGA arbiter client on register_device() failure
Description
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.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64475
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest patched version.
- Verify VGA arbiter registration and unwind paths.
- Test device registration and driver data handling.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64475.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64475 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64475
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64475 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64475 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '87856f9af04eaacf9848710625a4ffee1d020fa9', 'lessThan': '0f2a35a0c7ea7da347b814750eaa78adf3582381', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': '8d65decde9afd2bd78bcfffdc0df73b82a0b5509', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': 'ef4c38d30b3744e89eb5048218904bb629ea8d47', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': '9e0a3f642e607848669235f5069f35640abbfc88', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': '42d758a09d2c46c42357ecde9a5492f015bde2e5', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': '52adb2dff7ce3d8430e2bdc5988b618a430def85', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': '278a5659c391fe5afe5f9ce1bad1fd24e90144f1', 'versionType': 'git'}, {'status': 'affected', 'version': '4aeec3984ddc853f7c65903bde472ffdef738bae', 'lessThan': 'daedde7f024ecf88bc8e832ed40cf2c795f0796a', 'versionType': 'git'}, {'status': 'affected', 'version': 'd62dccb417cf972c978bf3c68a7d5e846bcf953e', 'versionType': 'git'}, {'status': 'affected', 'version': '6694b8daffac5a8661071f085608afc78f7acd08', 'versionType': 'git'}, {'status': 'affected', 'version': '5.10.37', 'lessThan': '5.10.261', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.11.21', 'lessThan': '5.12', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.12.4', 'lessThan': '5.13', 'versionType': 'semver'}], 'programFiles': ['drivers/vfio/pci/vfio_pci_core.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.13'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.13', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/vfio/pci/vfio_pci_core.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/0f2a35a0c7ea7da347b814750eaa78adf3582381 Added Reference https://git.kernel.org/stable/c/278a5659c391fe5afe5f9ce1bad1fd24e90144f1 Added Reference https://git.kernel.org/stable/c/42d758a09d2c46c42357ecde9a5492f015bde2e5 Added Reference https://git.kernel.org/stable/c/52adb2dff7ce3d8430e2bdc5988b618a430def85 Added Reference https://git.kernel.org/stable/c/8d65decde9afd2bd78bcfffdc0df73b82a0b5509 Added Reference https://git.kernel.org/stable/c/9e0a3f642e607848669235f5069f35640abbfc88 Added Reference https://git.kernel.org/stable/c/daedde7f024ecf88bc8e832ed40cf2c795f0796a Added Reference https://git.kernel.org/stable/c/ef4c38d30b3744e89eb5048218904bb629ea8d47