CVE-2026-68260: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-qrmv-vc96-x8hw
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-68260 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68260 at a Glance

CVE Identifier CVE-2026-68260
GHSA Identifier GHSA-qrmv-vc96-x8hw
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

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).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-68260

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.

Verify Direct and Transitive Dependencies

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-68260, 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

In the Linux kernel, the following vulnerability has been resolved: drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM The drm gpuvm code doesn't protect find operation against map operation, and the driver needs to ensure a map operation shouldn't happen when a find operation is in progress. In some cases a find operation will be in progress when doing map/unmap operations, and the find operation will do a NULL pointer dereference. An example of the stack trace of such NULL dereference is shown below: ``` Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000000010 [<ffffffff01e989d4>] drm_gpuva_find+0x28/0x6c [drm_gpuvm] [<ffffffff01ed3a40>] pvr_vm_unmap+0x34/0x68 [powervr] [<ffffffff01ec69da>] pvr_ioctl_vm_unmap+0x2e/0x50 [powervr] [<ffffffff8080ce0a>] drm_ioctl_kernel+0x8e/0xdc [<ffffffff8080d016>] drm_ioctl+0x1be/0x3e0 [<ffffffff802bec3e>] __riscv_sys_ioctl+0xba/0xc4 [<ffffffff80d858b2>] do_trap_ecall_u+0x23e/0x3f4 [<ffffffff80d92288>] handle_exception+0x168/0x174 ``` As all occurences of drm_gpuva_find*() are already guarded by vm_ctx->lock, make pvr_vm_map() to acquire this lock to prevent disturbing any find operation. This fixes the NULL deference problem in drm_gpuva_find*().

References

NVD — CVE-2026-68260 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68260
git.kernel.org/stable/c/15f58d44c2... WEB
https://git.kernel.org/stable/c/15f58d44c24477a6ebffa44ec05207b81cfa55d9
git.kernel.org/stable/c/17e2030f37... WEB
https://git.kernel.org/stable/c/17e2030f37600994440f875dc410615d5c66ee6d
git.kernel.org/stable/c/1f1f2618e4... WEB
https://git.kernel.org/stable/c/1f1f2618e44b21a7d4eb30d3bbd7e015ffbbbadf
git.kernel.org/stable/c/6253bb56bb... WEB
https://git.kernel.org/stable/c/6253bb56bb2ebdf317d8b599ce737a2510cc2e17

Frequently Asked Questions

What is CVE-2026-68260?
CVE-2026-68260 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68260?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-68260?
CVE-2026-68260 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-68260?
CVE-2026-68260 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68260?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qrmv-vc96-x8hw",
  "modified" : "2026-08-14T00:31:54Z",
  "published" : "2026-08-10T15:33:43Z",
  "aliases" : [ "CVE-2026-68260" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM\n\nThe drm gpuvm code doesn't protect find operation against map operation,\nand the driver needs to ensure a map operation shouldn't happen when a\nfind operation is in progress.\n\nIn some cases a find operation will be in progress when doing map/unmap\noperations, and the find operation will do a NULL pointer dereference.\n\nAn example of the stack trace of such NULL dereference is shown below:\n\n```\nUnable to handle kernel access to user memory without uaccess routines at\nvirtual address 0000000000000010\n\n[<ffffffff01e989d4>] drm_gpuva_find+0x28/0x6c [drm_gpuvm]\n[<ffffffff01ed3a40>] pvr_vm_unmap+0x34/0x68 [powervr]\n[<ffffffff01ec69da>] pvr_ioctl_vm_unmap+0x2e/0x50 [powervr]\n[<ffffffff8080ce0a>] drm_ioctl_kernel+0x8e/0xdc\n[<ffffffff8080d016>] drm_ioctl+0x1be/0x3e0\n[<ffffffff802bec3e>] __riscv_sys_ioctl+0xba/0xc4\n[<ffffffff80d858b2>] do_trap_ecall_u+0x23e/0x3f4\n[<ffffffff80d92288>] handle_exception+0x168/0x174\n```\n\nAs all occurences of drm_gpuva_find*() are already guarded by\nvm_ctx->lock, make pvr_vm_map() to acquire this lock to prevent\ndisturbing any find operation. This fixes the NULL deference problem in\ndrm_gpuva_find*().",
  "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-68260"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/15f58d44c24477a6ebffa44ec05207b81cfa55d9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/17e2030f37600994440f875dc410615d5c66ee6d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1f1f2618e44b21a7d4eb30d3bbd7e015ffbbbadf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6253bb56bb2ebdf317d8b599ce737a2510cc2e17"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:14Z"
  }
}