CVE-2026-64476: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-mcmr-g6rj-vcxr
Share
Published
Advisory Summary

CVE-2026-64476 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64476 at a Glance

CVE Identifier CVE-2026-64476
GHSA Identifier GHSA-mcmr-g6rj-vcxr
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-64476

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-64476, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-64476 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64476
git.kernel.org/stable/c/062b820290... WEB
https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb
git.kernel.org/stable/c/332d785f9a... WEB
https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3
git.kernel.org/stable/c/4575e9aac5... WEB
https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3
git.kernel.org/stable/c/654710ef31... WEB
https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8
git.kernel.org/stable/c/b98296816d... WEB
https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505
git.kernel.org/stable/c/f6c67cf005... WEB
https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2

Frequently Asked Questions

What is CVE-2026-64476?
CVE-2026-64476 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64476?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-64476?
CVE-2026-64476 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-64476?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mcmr-g6rj-vcxr",
  "modified" : "2026-07-25T12:31:37Z",
  "published" : "2026-07-25T12:31:37Z",
  "aliases" : [ "CVE-2026-64476" ],
  "details" : "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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64476"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/062b820290bcb9778e43a73597df76e9bb08acfb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/332d785f9ae426eeeb92527872adf09d84101ba3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4575e9aac5336d1365138c0284773bf8da4b1fa3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/654710ef3135c4546b20a903bc23a51b0c44d6c8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b98296816d31441b307ef9fa8670dcf5a55e5505"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f6c67cf0051f96ba61d186731d3d9409b9927db2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:33Z"
  }
}