CVE-2026-64376: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-vfm9-vf3r-mgwg
Share
CVSS 5.5
Published
Advisory Summary

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

CVE-2026-64376 at a Glance

CVE Identifier CVE-2026-64376
GHSA Identifier GHSA-vfm9-vf3r-mgwg
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-64376

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-64376, 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: firmware_loader: fix device reference leak in firmware_upload_register() firmware_upload_register() -> fw_create_instance() -> device_initialize() After fw_create_instance() succeeds, the lifetime of the embedded struct device is expected to be managed through the device core reference counting, since fw_create_instance() has already called device_initialize(). In firmware_upload_register(), if alloc_lookup_fw_priv() fails after fw_create_instance() succeeds, the code reaches free_fw_sysfs and frees fw_sysfs directly instead of releasing the device reference with put_device(). This may leave the reference count of the embedded struct device unbalanced, resulting in a refcount leak. The issue was identified by a static analysis tool I developed and confirmed by manual review. Fix this by using put_device(fw_dev) in the failure path and letting fw_dev_release() handle the final cleanup, instead of freeing the instance directly from the error path.

References

NVD — CVE-2026-64376 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64376
git.kernel.org/stable/c/15432f1956... WEB
https://git.kernel.org/stable/c/15432f19562fdb9199cce6d9fc24db12c71ed574
git.kernel.org/stable/c/2619b47a0c... WEB
https://git.kernel.org/stable/c/2619b47a0c8114eef980a56ade7e3ef4b58eb384
git.kernel.org/stable/c/46d403da37... WEB
https://git.kernel.org/stable/c/46d403da376a8b7c1187193294953816e1a8d7fe
git.kernel.org/stable/c/517676ec7d... WEB
https://git.kernel.org/stable/c/517676ec7dfca064e08f94007a4abd21969de0a0
git.kernel.org/stable/c/896df22ee5... WEB
https://git.kernel.org/stable/c/896df22ee57648b0c505bd76ddbc6b2341834696
git.kernel.org/stable/c/92f41769e5... WEB
https://git.kernel.org/stable/c/92f41769e5fd16bcd9ba97500d0517332e0a5b45

Frequently Asked Questions

What is CVE-2026-64376?
CVE-2026-64376 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-64376?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-64376?
CVE-2026-64376 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64376?
CVE-2026-64376 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-64376?
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-vfm9-vf3r-mgwg",
  "modified" : "2026-09-08T15:31:27Z",
  "published" : "2026-07-25T12:31:33Z",
  "aliases" : [ "CVE-2026-64376" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware_loader: fix device reference leak in firmware_upload_register()\n\nfirmware_upload_register()\n  -> fw_create_instance()\n     -> device_initialize()\n\nAfter fw_create_instance() succeeds, the lifetime of the embedded struct\ndevice is expected to be managed through the device core reference\ncounting, since fw_create_instance() has already called\ndevice_initialize().\n\nIn firmware_upload_register(), if alloc_lookup_fw_priv() fails after\nfw_create_instance() succeeds, the code reaches free_fw_sysfs and frees\nfw_sysfs directly instead of releasing the device reference with\nput_device(). This may leave the reference count of the embedded struct\ndevice unbalanced, resulting in a refcount leak.\n\nThe issue was identified by a static analysis tool I developed and\nconfirmed by manual review. Fix this by using put_device(fw_dev) in the\nfailure path and letting fw_dev_release() handle the final cleanup,\ninstead of freeing the instance directly from the error path.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64376"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/15432f19562fdb9199cce6d9fc24db12c71ed574"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2619b47a0c8114eef980a56ade7e3ef4b58eb384"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/46d403da376a8b7c1187193294953816e1a8d7fe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/517676ec7dfca064e08f94007a4abd21969de0a0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/896df22ee57648b0c505bd76ddbc6b2341834696"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/92f41769e5fd16bcd9ba97500d0517332e0a5b45"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:20Z"
  }
}