CVE-2026-64418: Software Security Vulnerability Vulnerability
HIGHCVE-2026-64418 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-64418 at a Glance
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).
How to Fix CVE-2026-64418
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.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-64418, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. 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
References
Frequently Asked Questions
What is CVE-2026-64418?
Which Software versions are affected?
What version fixes CVE-2026-64418?
What is the CVSS score of CVE-2026-64418?
What CWE is associated with CVE-2026-64418?
How can I check Maven dependencies for CVE-2026-64418?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-q5wg-g4g8-xfhc",
"modified" : "2026-07-27T06:30:36Z",
"published" : "2026-07-25T12:31:34Z",
"aliases" : [ "CVE-2026-64418" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: shrinker: fix shrinker_info teardown race with expansion\n\nexpand_shrinker_info() iterates all visible memcgs under shrinker_mutex,\nincluding memcgs that have not finished ->css_online() yet.\n\nOnce pn->shrinker_info has been published, teardown must stay serialized\nwith expand_shrinker_info() until that memcg is either fully online or no\nlonger visible to iteration. Today alloc_shrinker_info() breaks that rule\nby dropping shrinker_mutex before freeing a partially initialized\nshrinker_info array, which may cause the following race:\n\nCPU0 CPU1\n==== ====\n\ncss_create\n--> list_add_tail_rcu(&css->sibling, &parent_css->children);\n online_css\n --> mem_cgroup_css_online\n --> alloc_shrinker_info\n --> alloc node0 info\n rcu_assign_pointer(C->node0->shrinker_info, old0)\n alloc node1 info -> FAIL -> goto err\n mutex_unlock(shrinker_mutex)\n\n shrinker_alloc()\n --> shrinker_memcg_alloc\n --> mutex_lock(shrinker_mutex)\n expand_shrinker_info\n --> mem_cgroup_iter see the memcg\n expand_one_shrinker_info\n --> old0 = C->node0->shrinker_info\n memcpy(new->unit, old0->unit, ...);\n\n free_shrinker_info\n --> kvfree(old0);\n\n /* double free !! */\n kvfree_rcu(old0, rcu);\n\nThe same problem exists later in mem_cgroup_css_online(). If\nalloc_shrinker_info() succeeds but a subsequent objcg allocation fails,\nthe free_objcg -> free_shrinker_info() unwind path tears down the already\npublished pn->shrinker_info arrays without shrinker_mutex. The\nexpand_one_shrinker_info() can race with that teardown in the same way,\nleading to use-after-free or double-free of the old shrinker_info.\n\nFix this by serializing shrinker_info teardown with shrinker_mutex, and by\nkeeping alloc_shrinker_info() error cleanup inside the locked section.",
"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-64418"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/284c267f013e45d8c89d9fb9373105dc8e6c0947"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6465ff3ce65131c774a312d450abe10f4b9f3875"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/65476d31d8056e859c48580f82295ce159196ffe"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b9a280a9a454ed514636351d53fe2a233dc5054b"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-07-25T10:17:25Z"
}
}