CVE-2026-64071: Software Security Vulnerability Vulnerability
HIGHCVE-2026-64071 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-416: Use After Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-64071 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-64071
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-64071, 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-416: Use After Free, where the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. 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-64071?
Which Software versions are affected?
What version fixes CVE-2026-64071?
What is the CVSS score of CVE-2026-64071?
What CWE is associated with CVE-2026-64071?
How can I check Maven dependencies for CVE-2026-64071?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g774-9rm3-mcq6",
"modified" : "2026-09-03T15:32:00Z",
"published" : "2026-07-19T18:31:51Z",
"aliases" : [ "CVE-2026-64071" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: fix use-after-free in nvme_free_host_mem()\n\nnvme_free_host_mem() frees dev->hmb_sgt via dma_free_noncontiguous()\nbut never clears the pointer afterward. This leads to a use-after-free\nif nvme_free_host_mem() is called twice in the same error path.\n\nThis can happen during nvme_probe() when nvme_setup_host_mem() succeeds\nin allocating the HMB (setting dev->hmb_sgt) but nvme_set_host_mem()\nfails with an I/O error:\n\n nvme_setup_host_mem()\n nvme_alloc_host_mem_single() -> sets dev->hmb_sgt\n nvme_set_host_mem() -> fails with -EIO\n nvme_free_host_mem() -> frees hmb_sgt, but does NOT NULL it\n return error\n\n nvme_probe() error path:\n nvme_free_host_mem() -> dev->hmb_sgt is stale, use-after-free\n\nThe second call dereferences the freed sgt, causing a NULL pointer\ndereference in iommu_dma_free_noncontiguous() when it accesses\nsgt->sgl->dma_address (the backing memory has been freed and zeroed).\n\nThis is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC\nEnvoy Express behind a Dell WD22TB4 dock) where the device intermittently\nreturns I/O errors during HMB setup due to PCIe link instability.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000010\n RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80\n Call Trace:\n <TASK>\n dma_free_noncontiguous+0x3b/0x130\n nvme_free_host_mem+0x30/0xf0 [nvme]\n nvme_probe.cold+0xcc/0x275 [nvme]\n local_pci_probe+0x43/0xa0\n pci_device_probe+0xeea/0x290\n really_probe+0xf9/0x3b0\n __driver_probe_device+0x8b/0x170\n driver_probe_device+0x24/0xd0\n __driver_attach_async_helper+0x6b/0x110\n async_run_entry_fn+0x37/0x170\n process_one_work+0x1ac/0x3d0\n worker_thread+0x1b8/0x360\n kthread+0xf7/0x130\n ret_from_fork+0x2d8/0x3a0\n ret_from_fork_asm+0x1a/0x30\n </TASK>\n\nFix this by setting dev->hmb_sgt to NULL after freeing it, so the\nsecond call takes the multi-descriptor path which safely handles the\nalready-cleaned-up state.",
"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-64071"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7c89f474005d8377525d2991930b7432ee193a52"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9525e3a6fbb1d126a22ab2ee86ddea25af581a7c"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b35a13036755c5803168a7cb93bc66035c3e65b8"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-416" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-07-19T16:17:47Z"
}
}