CVE-2026-64475

HIGHCVSS 8.8/10EPSS 0.18%

Last modified

CVE-2026-64475 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
8.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS Probability
0.18%

8.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 87856f9af04eaacf9848710625a4ffee1d020fa9, < 0f2a35a0c7ea7da347b814750eaa78adf3582381; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < 8d65decde9afd2bd78bcfffdc0df73b82a0b5509; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < ef4c38d30b3744e89eb5048218904bb629ea8d47; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < 9e0a3f642e607848669235f5069f35640abbfc88; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < 42d758a09d2c46c42357ecde9a5492f015bde2e5; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < 52adb2dff7ce3d8430e2bdc5988b618a430def85; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < 278a5659c391fe5afe5f9ce1bad1fd24e90144f1; >= 4aeec3984ddc853f7c65903bde472ffdef738bae, < daedde7f024ecf88bc8e832ed40cf2c795f0796a; d62dccb417cf972c978bf3c68a7d5e846bcf953e; 6694b8daffac5a8661071f085608afc78f7acd08; >= 5.10.37, < 5.10.261; >= 5.11.21, < 5.12; >= 5.12.4, < 5.13
LinuxLinux5.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-64475?
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.
How severe is CVE-2026-64475?
CVE-2026-64475 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64475?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64475?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST