CVE-2026-64377: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-9gw4-rc8j-j633
Share
CVSS 7.8
CWE-415
Published
Advisory Summary

CVE-2026-64377 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-415: Double Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product calls free() twice on the same memory address.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64377 at a Glance

CVE Identifier CVE-2026-64377
GHSA Identifier GHSA-9gw4-rc8j-j633
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-415: Double Free
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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:H/I:H/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 High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-64377

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-64377, 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 CWE-415: Double Free, where the product calls free() twice on the same memory address. 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: cpufreq: qcom-cpufreq-hw: Fix possible double free qcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an array of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to one element of this array in policy->driver_data. qcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base. Remove the kfree(data) call and let devres release qcom_cpufreq.data. This issue was found by a static analysis tool I am developing.

References

NVD — CVE-2026-64377 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64377
git.kernel.org/stable/c/28a03a3f6e... WEB
https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13
git.kernel.org/stable/c/9de568ef6c... WEB
https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d
git.kernel.org/stable/c/bcb8889c49... WEB
https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2
git.kernel.org/stable/c/e904961332... WEB
https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489

Frequently Asked Questions

What is CVE-2026-64377?
CVE-2026-64377 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-415: Double Free.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64377?
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-64377?
CVE-2026-64377 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-64377?
CVE-2026-64377 is classified under CWE-415: Double Free (The product calls free() twice on the same memory address.).
How can I check Maven dependencies for CVE-2026-64377?
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-9gw4-rc8j-j633",
  "modified" : "2026-09-08T15:31:27Z",
  "published" : "2026-07-25T12:31:33Z",
  "aliases" : [ "CVE-2026-64377" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom-cpufreq-hw: Fix possible double free\n\nqcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an\narray of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to\none element of this array in policy->driver_data.\n\nqcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data.\nThis is not valid because the memory is devm-managed. For the first\ndomain, this can free the devm-managed allocation while the devres entry\nis still active, leading to a possible double free when the platform\ndevice is later detached. For other domains, the pointer may refer to an\nelement inside the array rather than the allocation base.\n\nRemove the kfree(data) call and let devres release qcom_cpufreq.data.\n\nThis issue was found by a static analysis tool I am developing.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64377"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-415" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-25T10:17:20Z"
  }
}