CVE-2026-64476: Linux kernel · vfio/pci: Latch disable_idle_d3 per device
Affects Linux kernelSource GCVE Database
Not known to be exploited · fixed in 6.8.0-147.147 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 11:52 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-147.147, 6.8.0-1067.70, 7.0.0-1012.12~24.04.1 +28
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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8917-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and included in Linux kernel versions 6.8.0-147.147, 6.8.0-1067.70, 7.0.0-1012.12~24.04.1, and others as listed in the fixedVersions. Users should update to these fixed kernel versions to resolve the issue. No additional mitigation steps are required beyond applying the official kernel updates.
Description
A vulnerability in the Linux kernel's vfio-pci driver related to the handling of the disable_idle_d3 flag has been resolved. The issue involved the flag being globally latched at module initialization rather than per device, causing unbalanced power management operations and inconsistent device power state handling. This could lead to unstable power management behavior for devices bound to vfio-pci variant drivers. The fix ensures the disable_idle_d3 flag is stored per device at initialization, maintaining consistent operation and balanced runtime power management calls.
References
- ubuntu.com/security/CVE-2026-64476 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-64476 (opens in a new tab)
- git.kernel.org/linus/4575e9aac5336d1365138c0284773bf8da4b1fa3 (opens in a new tab)
- git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb (opens in a new tab)
- git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3 (opens in a new tab)
- git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3 (opens in a new tab)
- git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8 (opens in a new tab)
- git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505 (opens in a new tab)
- git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-3 (opens in a new tab)