VulnerabilityPublished 25 Jul 2026Updated 17 Aug 2026

CVE-2026-64476: Linux kernel · vfio/pci: Latch disable_idle_d3 per device

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 3 Nov 2026, 19:29 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented that latches the disable_idle_d3 flag per device at initialization, ensuring consistent power management behavior. Users should update to the Linux kernel version containing this fix. Since this is a kernel-level fix, applying the official kernel update or backport is the recommended remediation. No additional mitigation steps are specified.

Description

CVE-2026-64476 addresses a Linux kernel vulnerability in the vfio-pci driver related to the disable_idle_d3 flag handling. The issue stems from the flag being globally latched at module initialization rather than per device, causing unbalanced runtime power management operations. The fix involves making disable_idle_d3 a per-device flag latched at device initialization to ensure consistent power state management.

Impact

The vulnerability could cause unbalanced runtime power management operations on devices bound to vfio-pci drivers due to the global handling of the disable_idle_d3 flag. This may lead to inconsistent device power states and potential instability in device power management. There is no indication of direct security exploitation or data compromise. No known exploits in the wild have been reported.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2026, 19:29 UTC

Technical details

References

Community reviews

Related threats