CVE-2026-64476
Received Received - Intake

Race Condition in Linux Kernel VFIO PCI Driver

Vulnerability report for CVE-2026-64476, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Latch disable_idle_d3 per device When disable_idle_d3 was introduced in vfio-pci, it directly manipulated the device power state with pci_set_power_state(). There were no refcounts to maintain or balanced operations, we could unconditionally bring the device to D0 and conditionally move it to D3hot. Therefore the module parameter was made writable. Later, in commit c61302aa48f7 ("vfio/pci: Move module parameters to vfio_pci.c"), as part of the vfio-pci-core split, the writable aspect of the module parameter was nullified. The parameter value could still be changed through sysfs, but the vfio-pci driver latched the values into vfio-pci-core globals at module init. Loading the vfio-pci module, or unloading and reloading, with non-default or different values could change the globals relative to existing devices bound to vfio-pci variant drivers. Runtime PM was introduced in commit 7ab5e10eda02 ("vfio/pci: Move the unused device into low power state with runtime PM"), which marks the point where power states became refcounted. PM get and put operations need to be balanced, but the same module operations noted above can change the global variables relative to those devices already bound to vfio-pci variant drivers. This introduces a window where PM operations can now become unbalanced. To resolve this with a narrow footprint for stable backports, the disable_idle_d3 flag is latched into the vfio_pci_core_device at the time of initialization, such that the device always operates with a consistent value. NB. vfio_pci_dev_set_try_reset() now unconditionally raises the runtime PM usage count around bus reset to account for disable_idle_d3 becoming a per-device rather than global flag. When this flag is set, the additional get/put pair is harmless and allows continued use of the shared vfio_pci_dev_set_pm_runtime_get() helper.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-25
Generated
2026-07-25
AI Q&A
2026-07-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel vfio_pci *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper handling of the disable_idle_d3 module parameter in the vfio-pci driver. The issue arises because the parameter was initially writable but later became latched into global variables during module initialization. This creates a mismatch between the global settings and per-device operations, leading to unbalanced power management (PM) operations. Specifically, runtime PM refcounts can become unbalanced when the global disable_idle_d3 setting changes relative to devices already bound to vfio-pci drivers.

Detection Guidance

This vulnerability is specific to the Linux kernel's vfio-pci driver and requires checking kernel module parameters and device states. Inspect the disable_idle_d3 parameter in /sys/module/vfio_pci/parameters/disable_idle_d3 and compare it with the current device power states. Use commands like 'cat /sys/module/vfio_pci/parameters/disable_idle_d3' and 'lspci -vvv' to check device power states.

Impact Analysis

This vulnerability could lead to system instability or crashes due to unbalanced power management operations. If the disable_idle_d3 setting is changed after devices are bound to vfio-pci drivers, it may cause improper power state transitions, potentially disrupting device functionality or leading to kernel panics. Systems relying on vfio-pci for virtualization or device passthrough may experience unexpected behavior or failures.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for this vulnerability. If updating is not immediately possible, avoid changing the disable_idle_d3 parameter after module initialization to prevent power state inconsistencies. Monitor devices bound to vfio-pci for unexpected power state changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64476. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart