CVE-2026-68103: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-wgx5-5x9q-wrw8
Share
CVSS 7.1
CWE-662
Published
Advisory Summary

CVE-2026-68103 is a HIGH (CVSS 7.1) security vulnerability vulnerability (CWE-662: Improper Synchronization) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68103 at a Glance

CVE Identifier CVE-2026-68103
GHSA Identifier GHSA-wgx5-5x9q-wrw8
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-662: Improper Synchronization
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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:N/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 None (C:N)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-68103

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-68103, 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 CWE-662: Improper Synchronization, where the product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes. 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/amdgpu: reject mapping a reserved doorbell to a new queue When creating an user-queue, the user space provides a doorbell BO handle and an offset within the bo to obtain a doorbell. However current implementation using xa_store_irq() to store a doorbell, which allows a later queue created with the same BO and offset parameters to overwrite an existing queue and doorbell mapping. This can cause problems like misrouting fence IRQ processing to a wrong queue, and mislead the cleanup process of one queue erasing the mapping of another queue. This commit fixes this issue by replacing xa_store_irq with xa_insert_irq, which rejects mapping a reserved doorbell to a newly created queue (cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)

References

NVD — CVE-2026-68103 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68103
git.kernel.org/stable/c/1050d258c7... WEB
https://git.kernel.org/stable/c/1050d258c7c56066d2dcaedf8d0ef66364062adc
git.kernel.org/stable/c/a609b6278b... WEB
https://git.kernel.org/stable/c/a609b6278bf3cde17eeee6620091465521e4b02c

Frequently Asked Questions

What is CVE-2026-68103?
CVE-2026-68103 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-662: Improper Synchronization.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68103?
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-68103?
CVE-2026-68103 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.
What CWE is associated with CVE-2026-68103?
CVE-2026-68103 is classified under CWE-662: Improper Synchronization (The product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.).
How can I check Maven dependencies for CVE-2026-68103?
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-wgx5-5x9q-wrw8",
  "modified" : "2026-08-14T00:31:51Z",
  "published" : "2026-08-10T15:33:35Z",
  "aliases" : [ "CVE-2026-68103" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: reject mapping a reserved doorbell to a new queue\n\nWhen creating an user-queue, the user space\nprovides a doorbell BO handle and an offset within\nthe bo to obtain a doorbell.\n\nHowever current implementation using xa_store_irq()\nto store a doorbell, which allows a later queue created\nwith the same BO and offset parameters to overwrite an\nexisting queue and doorbell mapping.\n\nThis can cause problems like misrouting fence IRQ\nprocessing to a wrong queue, and mislead the cleanup\nprocess of one queue erasing the mapping of another queue.\n\nThis commit fixes this issue by replacing xa_store_irq with\nxa_insert_irq, which rejects mapping a reserved\ndoorbell to a newly created queue\n\n(cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68103"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1050d258c7c56066d2dcaedf8d0ef66364062adc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a609b6278bf3cde17eeee6620091465521e4b02c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-662" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:19:54Z"
  }
}