In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The… (CVE-2026-64475)
A vulnerability in the Linux kernel's vfio/pci subsystem involves improper release of the VGA arbiter client on register_device() failure. The issue stems from a missing unwind callout after a re-ordering of failure points in vfio_pci_core_register_device(), which could leave a stale callback referencing freed memory. This stale registration may become unsafe if the callback accesses the vfio device data. The vulnerability has been resolved by adding the necessary VGA arbiter client release during failure handling.
AI Analysis
Technical Summary
The Linux kernel vfio/pci component had a flaw where, due to a code re-ordering, the VGA arbiter client was not released properly on register_device() failure. This omission could leave a callback with a freed vdev cookie, creating a stale registration that risks unsafe memory access when the callback follows driver data to the vfio device. The fix involves adding the required VGA arbiter unwind callout to ensure proper cleanup on failure paths.
Potential Impact
The vulnerability could lead to unsafe memory access due to a stale callback referencing freed resources in the vfio/pci subsystem. While current kernels mostly mitigate this risk because of pci_dev state usage, the original failure path could cause use-after-free conditions, potentially leading to kernel instability or other undefined behavior.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding the required VGA arbiter client release on register_device() failure. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory or Linux kernel mailing lists for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The… (CVE-2026-64475)
Description
A vulnerability in the Linux kernel's vfio/pci subsystem involves improper release of the VGA arbiter client on register_device() failure. The issue stems from a missing unwind callout after a re-ordering of failure points in vfio_pci_core_register_device(), which could leave a stale callback referencing freed memory. This stale registration may become unsafe if the callback accesses the vfio device data. The vulnerability has been resolved by adding the necessary VGA arbiter client release during failure handling.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vfio/pci component had a flaw where, due to a code re-ordering, the VGA arbiter client was not released properly on register_device() failure. This omission could leave a callback with a freed vdev cookie, creating a stale registration that risks unsafe memory access when the callback follows driver data to the vfio device. The fix involves adding the required VGA arbiter unwind callout to ensure proper cleanup on failure paths.
Potential Impact
The vulnerability could lead to unsafe memory access due to a stale callback referencing freed resources in the vfio/pci subsystem. While current kernels mostly mitigate this risk because of pci_dev state usage, the original failure path could cause use-after-free conditions, potentially leading to kernel instability or other undefined behavior.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding the required VGA arbiter client release on register_device() failure. Users should apply the official kernel updates that include this patch. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory or Linux kernel mailing lists for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mj56-4c42-9869
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64475"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542069c2644c7f808239b
Added to database: 07/25/2026, 23:08:54 UTC
Last enriched: 07/25/2026, 23:16:32 UTC
Last updated: 07/26/2026, 03:56:00 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.