CVE-2026-68275: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-68275 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-68275 at a Glance
How to Fix CVE-2026-68275
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-68275, 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-68275?
Which Software versions are affected?
What version fixes CVE-2026-68275?
What CWE is associated with CVE-2026-68275?
How can I check Maven dependencies for CVE-2026-68275?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4c3m-c328-j6mf",
"modified" : "2026-08-10T15:33:44Z",
"published" : "2026-08-10T15:33:44Z",
"aliases" : [ "CVE-2026-68275" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO\n\nThe AMDGPU_GEM_OP_GET_MAPPING_INFO path of amdgpu_gem_op_ioctl() looks\nup the bo_va for the buffer object in the caller's VM via\namdgpu_vm_bo_find(), but uses the returned pointer without checking it.\n\namdgpu_vm_bo_find() returns NULL when the BO has no bo_va in that VM,\nwhich is the normal case for a BO that has never been mapped. The result\nis fed straight into amdgpu_vm_bo_va_for_each_valid_mapping(), which\nexpands to list_for_each_entry(mapping, &(bo_va)->valids, list) and\ndereferences bo_va, causing a NULL pointer dereference.\n\nThis is reachable by any process able to issue the ioctl (render group)\nsimply by requesting mapping info for an unmapped BO.\n\nReturn -ENOENT when no bo_va is found, jumping to out_exec so the\ndrm_exec context and GEM object reference are released.\n\n(cherry picked from commit 528b19377affc1cc7362a70a254c1dda793595f9)",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68275"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/93475c34111916df71c63e510fc52db01351f809"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9faf4c66edb6bcb8ca0465c3a4868bb7f278cd31"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ddba17b3dfa0efc80d6c98621c2fb7af66adb622"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-10T13:20:16Z"
}
}