CVE-2026-68271: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-68271 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-68271 at a Glance
How to Fix CVE-2026-68271
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:tree
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-68271, 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
References
Frequently Asked Questions
What is CVE-2026-68271?
Which Software versions are affected?
What version fixes CVE-2026-68271?
What CWE is associated with CVE-2026-68271?
How can I check Maven dependencies for CVE-2026-68271?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hvp2-xg6j-p7j9",
"modified" : "2026-08-10T15:33:44Z",
"published" : "2026-08-10T15:33:44Z",
"aliases" : [ "CVE-2026-68271" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: fix reversed error cleanup order in ucopy functions\n\nnouveau_uvmm_vm_bind_ucopy() and nouveau_exec_ucopy() place their error\ncleanup labels in allocation order rather than reverse allocation order.\nOn a u_memcpya() failure for in_sync.s, the goto to err_free_ops (or\nerr_free_pushs) frees the first allocation and then falls through to\nerr_free_ins, which calls u_free() on args->in_sync.s.\n\nSince args->in_sync.s still holds the ERR_PTR returned by the failed\nu_memcpya(), and ERR_PTR values are not caught by ZERO_OR_NULL_PTR(),\nkvfree() proceeds to dereference it, which can result in a kernel oops.\nA failure for out_sync.s instead jumps to err_free_ins and skips freeing\nthe first allocation, leading to a memory leak.\n\nFix by swapping the cleanup label order so resources are freed in the\ncorrect reverse allocation sequence.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68271"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/2473ac314387a5def7244eb6d6a345934ed140bf"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4e109faa9ea2b6c04cc5a99e76db3126575a59d1"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ab99ead646b1b833ecd57fe577a2816f2e848167"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e15c25c7972d38a9f6bf8c3f7f29179a67263eba"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ebbaf64d2635d1e78196c067fa8fa582a7dc17f7"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-10T13:20:16Z"
}
}