CVE-2026-64210: Software Security Vulnerability Vulnerability
HIGHCVE-2026-64210 is a HIGH (CVSS 7.5) 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-64210 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2026-64210
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-64210, 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-64210?
Which Software versions are affected?
What version fixes CVE-2026-64210?
What is the CVSS score of CVE-2026-64210?
What CWE is associated with CVE-2026-64210?
How can I check Maven dependencies for CVE-2026-64210?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-p5xx-69g5-8564",
"modified" : "2026-09-14T12:31:31Z",
"published" : "2026-07-24T18:31:26Z",
"aliases" : [ "CVE-2026-64210" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: xsk: Fix unlocked writing to ICOSQ\n\nDuring napi poll, when the affinity changes and there's still XSK work\nto be done, we trigger an ICOSQ interrupt on the new CPU. However, this\ntriggering on the ICOSQ is done unprotected.\n\nThere are 2 such races:\n\nA) mlx5e_trigger_irq() is called while mlx5e_xsk_alloc_rx_mpwqe() is\nrunning from a different CPU due to affinity change. This can happen\nbecause IRQ triggering is done after napi_complete_done(). At this point\nthe NAPI can be scheduled on a different CPU. Like this:\n\n CPU A (old affinity, NAPI tail) CPU B (new affinity, fresh NAPI)\n ------------------------------- --------------------------------\n napi_complete_done() clears SCHED\n mlx5e_cq_arm(...)\n napi_schedule_prep() sets SCHED\n mlx5e_napi_poll()\n mlx5e_xsk_alloc_rx_mpwqe()\n mlx5e_icosq_sync_lock() // noop\n memcpy 640 B UMR body\n advance sq->pc by 10\n mlx5e_trigger_irq(&c->icosq)\n wqe_info[pi] = {NOP, 1}\n mlx5e_post_nop() advances sq->pc\n\nB) mlx5e_trigger_irq() is called on the ICOSQ when\nmlx5e_trigger_napi_icosq() is running.\n\nThe obvious fix would be to lock the ICOSQ. But ICOSQ has an optimized\nlocking scheme that doesn't work for this scenario. Kick the async ICOSQ\ninstead which is always locked.\n\nThis issue was noticed in the wild with the following splat:\n\n netdevice: ge-0-0-1: Bad OP in ICOSQ CQE: 0xd\n WARNING: drivers/net/ethernet/mellanox/mlx5/core/en_rx.c:826 [...]\n [...]\n Call Trace:\n <IRQ>\n mlx5e_napi_poll+0x11d/0x7f0 [mlx5_core]\n __napi_poll+0x30/0x200\n ? skb_defer_free_flush+0x9c/0xc0\n net_rx_action+0x2fe/0x3f0\n handle_softirqs+0xd8/0x340\n __irq_exit_rcu+0xbc/0xe0\n common_interrupt+0x85/0xa0\n </IRQ>\n <TASK>\n asm_common_interrupt+0x26/0x40\n [...]\n ---[ end trace 0000000000000000 ]---\n mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2022, qn 0x8f4,\n opcode 0xd, syndrome 0x2, vendor syndrome 0x68\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000030: 00 00 00 00 01 00 68 02 01 00 08 f4 de 14 59 d2\n WQE DUMP: WQ size 16384 WQ cur size 0, WQE index 0x1e14, len: 64\n 00000000: 00 00 00 01 d9 ed 80 02 00 00 00 01 d9 ed 90 02\n 00000010: 00 00 00 01 d9 ed a0 02 00 00 00 01 d9 ed b0 02\n 00000020: 00 00 00 01 d9 ed c0 02 00 00 00 01 d9 ed d0 02\n 00000030: 00 00 00 01 d9 ed e0 02 00 00 00 01 d9 ed f0 02\n mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2023, qn 0x8f4,\n opcode 0xd, syndrome 0x5, vendor syndrome 0xf9\n 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 00000030: 00 00 00 00 01 00 f9 05 01 00 08 f4 de 15 cf d2",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64210"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/0c8f331485656d5937d56a488016b944a038fe2f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/54a97ef1025236cc1bc54d79c7ae2eb8027ce4b8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/8d3b91e7d81000d295cd914d4d9d6f860252e2bf"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c326f9c68921e2f14dfcecb2f6b4216313d50248"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f37adef34eb7ebe29a534d20ccadd72bd7ff664e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f3d8c2fd591bb603b069e151881a317e26a3f478"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-362" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-07-24T16:16:48Z"
}
}