CVE-2026-93047: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-75w8-rpch-q4h9
Share
Published
Advisory Summary

CVE-2026-93047 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-93047 at a Glance

CVE Identifier CVE-2026-93047
GHSA Identifier GHSA-75w8-rpch-q4h9
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-93047

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-93047, 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/v3d: Associate BOs with every job that accesses them A submission can expand into a chain of jobs (e.g. bin + render + cache clean). Implicit synchronization in v3d_submit_lock_reservations() is gated on each job's bo[], but the BO list was only ever attached to the last job of the chain. When that last job is a trailing CACHE_CLEAN job, the job that actually consumes the BOs (that is, a RENDER or CSD job) was left with bo_count == 0 and picked up no implicit dependencies. It could therefore be dispatched to the hardware and read a BO while another context was still writing it, leading to data corruption. Attach the BOs to the job that consumes them, so (1) it acquires the correct implicit dependencies during reservation locking and (2) they are kept mapped until the end of the submission. Give it references to all consuming job's BOs through v3d_job_reference_bos() instead of looking the handles up a second time; that avoids a redundant lookup and guarantees both jobs reference the exact same objects. As the CACHE_CLEAN job now carries a BO array as well, add a per-job `has_implicit_dep` flag so that only the consuming jobs take implicit dependencies. The CACHE_CLEAN job (a global flush) and the BIN job (binning waiting on another context is not a realistic scenario) are excluded.

References

NVD — CVE-2026-93047 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93047
git.kernel.org/stable/c/7244dd0f12... WEB
https://git.kernel.org/stable/c/7244dd0f12629484a1936dc5c5837670d8d9f80c
git.kernel.org/stable/c/fa98563ab0... WEB
https://git.kernel.org/stable/c/fa98563ab00dbe62fcedfef6bdd34ded7a860d9f

Frequently Asked Questions

What is CVE-2026-93047?
CVE-2026-93047 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-93047?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93047?
CVE-2026-93047 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93047?
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-75w8-rpch-q4h9",
  "modified" : "2026-09-17T18:32:08Z",
  "published" : "2026-09-17T18:32:08Z",
  "aliases" : [ "CVE-2026-93047" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Associate BOs with every job that accesses them\n\nA submission can expand into a chain of jobs (e.g. bin + render + cache\nclean). Implicit synchronization in v3d_submit_lock_reservations() is gated\non each job's bo[], but the BO list was only ever attached to the last job\nof the chain. When that last job is a trailing CACHE_CLEAN job, the job\nthat actually consumes the BOs (that is, a RENDER or CSD job) was left with\nbo_count == 0 and picked up no implicit dependencies. It could therefore\nbe dispatched to the hardware and read a BO while another context was still\nwriting it, leading to data corruption.\n\nAttach the BOs to the job that consumes them, so (1) it acquires the\ncorrect implicit dependencies during reservation locking and (2) they are\nkept mapped until the end of the submission. Give it references to all\nconsuming job's BOs through v3d_job_reference_bos() instead of looking the\nhandles up a second time; that avoids a redundant lookup and guarantees\nboth jobs reference the exact same objects.\n\nAs the CACHE_CLEAN job now carries a BO array as well, add a per-job\n`has_implicit_dep` flag so that only the consuming jobs take implicit\ndependencies. The CACHE_CLEAN job (a global flush) and the BIN job (binning\nwaiting on another context is not a realistic scenario) are excluded.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93047"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7244dd0f12629484a1936dc5c5837670d8d9f80c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fa98563ab00dbe62fcedfef6bdd34ded7a860d9f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:57Z"
  }
}