{"api_version":"1","generated_at":"2026-08-02T17:55:27+00:00","cve":"CVE-2026-64476","urls":{"html":"https://cve.report/CVE-2026-64476","api":"https://cve.report/api/cve/CVE-2026-64476.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64476","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64476"},"summary":{"title":"vfio/pci: Latch disable_idle_d3 per device","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvfio/pci: Latch disable_idle_d3 per device\n\nWhen disable_idle_d3 was introduced in vfio-pci, it directly manipulated\nthe device power state with pci_set_power_state().  There were no\nrefcounts to maintain or balanced operations, we could unconditionally\nbring the device to D0 and conditionally move it to D3hot.  Therefore\nthe module parameter was made writable.\n\nLater, in commit c61302aa48f7 (\"vfio/pci: Move module parameters to\nvfio_pci.c\"), as part of the vfio-pci-core split, the writable aspect\nof the module parameter was nullified.  The parameter value could still\nbe changed through sysfs, but the vfio-pci driver latched the values\ninto vfio-pci-core globals at module init.  Loading the vfio-pci module,\nor unloading and reloading, with non-default or different values could\nchange the globals relative to existing devices bound to vfio-pci\nvariant drivers.\n\nRuntime PM was introduced in commit 7ab5e10eda02 (\"vfio/pci: Move the\nunused device into low power state with runtime PM\"), which marks the\npoint where power states became refcounted.  PM get and put operations\nneed to be balanced, but the same module operations noted above can\nchange the global variables relative to those devices already bound to\nvfio-pci variant drivers.  This introduces a window where PM operations\ncan now become unbalanced.\n\nTo resolve this with a narrow footprint for stable backports, the\ndisable_idle_d3 flag is latched into the vfio_pci_core_device at the\ntime of initialization, such that the device always operates with a\nconsistent value.\n\nNB. vfio_pci_dev_set_try_reset() now unconditionally raises the\nruntime PM usage count around bus reset to account for disable_idle_d3\nbecoming a per-device rather than global flag.  When this flag is set,\nthe additional get/put pair is harmless and allows continued use of the\nshared vfio_pci_dev_set_pm_runtime_get() helper.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:33","updated_at":"2026-07-25 10:17:33"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3","name":"https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2","name":"https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3","name":"https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8","name":"https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb","name":"https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505","name":"https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64476","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64476","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c 332d785f9ae426eeeb92527872adf09d84101ba3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c 654710ef3135c4546b20a903bc23a51b0c44d6c8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c b98296816d31441b307ef9fa8670dcf5a55e5505 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c f6c67cf0051f96ba61d186731d3d9409b9927db2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c 062b820290bcb9778e43a73597df76e9bb08acfb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7ab5e10eda02da1d9562ffde562c51055d368e9c 4575e9aac5336d1365138c0284773bf8da4b1fa3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.178 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.145 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.96 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.39 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64476","cve":"CVE-2026-64476","epss":"0.001800000","percentile":"0.079220000","score_date":"2026-07-28","updated_at":"2026-07-29 00:05:33"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/vfio/pci/vfio_pci_core.c","include/linux/vfio_pci_core.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"332d785f9ae426eeeb92527872adf09d84101ba3","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"},{"lessThan":"654710ef3135c4546b20a903bc23a51b0c44d6c8","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"},{"lessThan":"b98296816d31441b307ef9fa8670dcf5a55e5505","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"},{"lessThan":"f6c67cf0051f96ba61d186731d3d9409b9927db2","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"},{"lessThan":"062b820290bcb9778e43a73597df76e9bb08acfb","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"},{"lessThan":"4575e9aac5336d1365138c0284773bf8da4b1fa3","status":"affected","version":"7ab5e10eda02da1d9562ffde562c51055d368e9c","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/vfio/pci/vfio_pci_core.c","include/linux/vfio_pci_core.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.19"},{"lessThan":"5.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.178","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.145","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.96","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.39","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.178","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.145","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.96","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.39","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc2","versionStartIncluding":"5.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nvfio/pci: Latch disable_idle_d3 per device\n\nWhen disable_idle_d3 was introduced in vfio-pci, it directly manipulated\nthe device power state with pci_set_power_state().  There were no\nrefcounts to maintain or balanced operations, we could unconditionally\nbring the device to D0 and conditionally move it to D3hot.  Therefore\nthe module parameter was made writable.\n\nLater, in commit c61302aa48f7 (\"vfio/pci: Move module parameters to\nvfio_pci.c\"), as part of the vfio-pci-core split, the writable aspect\nof the module parameter was nullified.  The parameter value could still\nbe changed through sysfs, but the vfio-pci driver latched the values\ninto vfio-pci-core globals at module init.  Loading the vfio-pci module,\nor unloading and reloading, with non-default or different values could\nchange the globals relative to existing devices bound to vfio-pci\nvariant drivers.\n\nRuntime PM was introduced in commit 7ab5e10eda02 (\"vfio/pci: Move the\nunused device into low power state with runtime PM\"), which marks the\npoint where power states became refcounted.  PM get and put operations\nneed to be balanced, but the same module operations noted above can\nchange the global variables relative to those devices already bound to\nvfio-pci variant drivers.  This introduces a window where PM operations\ncan now become unbalanced.\n\nTo resolve this with a narrow footprint for stable backports, the\ndisable_idle_d3 flag is latched into the vfio_pci_core_device at the\ntime of initialization, such that the device always operates with a\nconsistent value.\n\nNB. vfio_pci_dev_set_try_reset() now unconditionally raises the\nruntime PM usage count around bus reset to account for disable_idle_d3\nbecoming a per-device rather than global flag.  When this flag is set,\nthe additional get/put pair is harmless and allows continued use of the\nshared vfio_pci_dev_set_pm_runtime_get() helper."}],"providerMetadata":{"dateUpdated":"2026-07-25T08:51:38.865Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3"},{"url":"https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8"},{"url":"https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505"},{"url":"https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2"},{"url":"https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb"},{"url":"https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3"}],"title":"vfio/pci: Latch disable_idle_d3 per device","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64476","datePublished":"2026-07-25T08:51:38.865Z","dateReserved":"2026-07-19T15:36:31.791Z","dateUpdated":"2026-07-25T08:51:38.865Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:33","lastModifiedDate":"2026-07-25 10:17:33","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64476","Ordinal":"1","Title":"vfio/pci: Latch disable_idle_d3 per device","CVE":"CVE-2026-64476","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64476","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nvfio/pci: Latch disable_idle_d3 per device\n\nWhen disable_idle_d3 was introduced in vfio-pci, it directly manipulated\nthe device power state with pci_set_power_state().  There were no\nrefcounts to maintain or balanced operations, we could unconditionally\nbring the device to D0 and conditionally move it to D3hot.  Therefore\nthe module parameter was made writable.\n\nLater, in commit c61302aa48f7 (\"vfio/pci: Move module parameters to\nvfio_pci.c\"), as part of the vfio-pci-core split, the writable aspect\nof the module parameter was nullified.  The parameter value could still\nbe changed through sysfs, but the vfio-pci driver latched the values\ninto vfio-pci-core globals at module init.  Loading the vfio-pci module,\nor unloading and reloading, with non-default or different values could\nchange the globals relative to existing devices bound to vfio-pci\nvariant drivers.\n\nRuntime PM was introduced in commit 7ab5e10eda02 (\"vfio/pci: Move the\nunused device into low power state with runtime PM\"), which marks the\npoint where power states became refcounted.  PM get and put operations\nneed to be balanced, but the same module operations noted above can\nchange the global variables relative to those devices already bound to\nvfio-pci variant drivers.  This introduces a window where PM operations\ncan now become unbalanced.\n\nTo resolve this with a narrow footprint for stable backports, the\ndisable_idle_d3 flag is latched into the vfio_pci_core_device at the\ntime of initialization, such that the device always operates with a\nconsistent value.\n\nNB. vfio_pci_dev_set_try_reset() now unconditionally raises the\nruntime PM usage count around bus reset to account for disable_idle_d3\nbecoming a per-device rather than global flag.  When this flag is set,\nthe additional get/put pair is harmless and allows continued use of the\nshared vfio_pci_dev_set_pm_runtime_get() helper.","Type":"Description","Title":"vfio/pci: Latch disable_idle_d3 per device"}]}}}