CVE-2026-64476vfio/pci: Latch disable_idle_d3 per device
- 5.5MediumCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
- 6 days later
· 6 days later
First scored
Medium 5.5
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < 332d785f9ae426eeeb92527872adf09d84101ba3
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < 654710ef3135c4546b20a903bc23a51b0c44d6c8
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < b98296816d31441b307ef9fa8670dcf5a55e5505
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < f6c67cf0051f96ba61d186731d3d9409b9927db2
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < 062b820290bcb9778e43a73597df76e9bb08acfb
- affected 7ab5e10eda02da1d9562ffde562c51055d368e9c – < 4575e9aac5336d1365138c0284773bf8da4b1fa3
- affected 5.19
- unaffected < 5.19
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3 (opens in a new tab)
- https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8 (opens in a new tab)
- https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505 (opens in a new tab)
- https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2 (opens in a new tab)
- https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb (opens in a new tab)
- https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48820 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64476)Record last updated .