CVE-2026-64475

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.

Is your site exposed to CVE-2026-64475?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0022

Probability of exploitation

0.13%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/0f2a35a0c7ea7da347b814750eaa78adf3582381 https://git.kernel.org/stable/c/278a5659c391fe5afe5f9ce1bad1fd24e90144f1 https://git.kernel.org/stable/c/42d758a09d2c46c42357ecde9a5492f015bde2e5 https://git.kernel.org/stable/c/52adb2dff7ce3d8430e2bdc5988b618a430def85 https://git.kernel.org/stable/c/8d65decde9afd2bd78bcfffdc0df73b82a0b5509 https://git.kernel.org/stable/c/9e0a3f642e607848669235f5069f35640abbfc88 https://git.kernel.org/stable/c/daedde7f024ecf88bc8e832ed40cf2c795f0796a https://git.kernel.org/stable/c/ef4c38d30b3744e89eb5048218904bb629ea8d47

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 do I check if I'm vulnerable to CVE-2026-64475? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.