CVE-2026-74453: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-3p68-w4fc-v365
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-74453
GHSA Identifier GHSA-3p68-w4fc-v365
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-74453

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-74453, 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/vc4: Zero the tile state data array before each BIN job The binner BO is a single 16MB buffer split into 512KB slots that are handed out to jobs at submission time and recycled as jobs complete, without ever being cleared. Each slot holds the job's Tile State Data Array (TSDA) at its start, followed by the tile allocation pool. While the tile allocation pool is only walked by the render thread through branches the binner generated during the current job, the TSDA is the PTB's own per-tile bookkeeping and is consumed by the hardware itself. Although the kernel sets the "Auto-initialise Tile State Data Array" flag in the tile binning mode configuration, the PTB demonstrably still acts on stale tile state left by the slot's previous user: the binner ends up creating invalid command streams with invalid primitive streams and branches, which can cause GPU hangs as observed in [1][2]. Zero the TSDA when the job's binning slot is configured. This clears 48 bytes per tile (~24KB for a 1080p frame) in the submission path, and guarantees the PTB never sees another job's tile state. The tile count is only checked for being non-zero today, so the 8-bit fields it comes from can describe a tile state array almost six times larger than the slot it has to live in. Bound it before the slot is handed out, since such size decides how much of the slot is left for the tile alloc pool.

References

NVD — CVE-2026-74453 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74453
git.kernel.org/stable/c/0e858422df... WEB
https://git.kernel.org/stable/c/0e858422df2334165293ea742da9fbb2e51f2739
git.kernel.org/stable/c/48a570c964... WEB
https://git.kernel.org/stable/c/48a570c964d8e37d353381e4195106277e17f5cb
git.kernel.org/stable/c/57667eb754... WEB
https://git.kernel.org/stable/c/57667eb7548faaac396c6e39f3b4444dab5b097c
git.kernel.org/stable/c/a75c8f365e... WEB
https://git.kernel.org/stable/c/a75c8f365e209aa9bb927b0942a7840152d44892
git.kernel.org/stable/c/c5d8e8e1a8... WEB
https://git.kernel.org/stable/c/c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea
git.kernel.org/stable/c/c8dea7e7c6... WEB
https://git.kernel.org/stable/c/c8dea7e7c6098e383e44f21a64d0431da5480e3f
git.kernel.org/stable/c/d3677372e0... WEB
https://git.kernel.org/stable/c/d3677372e0275e139f0efd2872c5a524b5d12868
git.kernel.org/stable/c/f5802be655... WEB
https://git.kernel.org/stable/c/f5802be65535f8818af7191159cf8c11f48ab2a2

Frequently Asked Questions

What is CVE-2026-74453?
CVE-2026-74453 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-74453?
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-74453?
CVE-2026-74453 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-74453?
CVE-2026-74453 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74453?
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-3p68-w4fc-v365",
  "modified" : "2026-08-19T18:32:27Z",
  "published" : "2026-08-15T15:30:32Z",
  "aliases" : [ "CVE-2026-74453" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: Zero the tile state data array before each BIN job\n\nThe binner BO is a single 16MB buffer split into 512KB slots that are\nhanded out to jobs at submission time and recycled as jobs complete,\nwithout ever being cleared. Each slot holds the job's Tile State Data\nArray (TSDA) at its start, followed by the tile allocation pool.\n\nWhile the tile allocation pool is only walked by the render thread\nthrough branches the binner generated during the current job, the\nTSDA is the PTB's own per-tile bookkeeping and is consumed by the\nhardware itself. Although the kernel sets the \"Auto-initialise Tile\nState Data Array\" flag in the tile binning mode configuration, the\nPTB demonstrably still acts on stale tile state left by the slot's\nprevious user: the binner ends up creating invalid command streams\nwith invalid primitive streams and branches, which can cause GPU hangs\nas observed in [1][2].\n\nZero the TSDA when the job's binning slot is configured. This clears\n48 bytes per tile (~24KB for a 1080p frame) in the submission path, and\nguarantees the PTB never sees another job's tile state.\n\nThe tile count is only checked for being non-zero today, so the 8-bit\nfields it comes from can describe a tile state array almost six times\nlarger than the slot it has to live in. Bound it before the slot is\nhanded out, since such size decides how much of the slot is left for\nthe tile alloc pool.",
  "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-74453"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0e858422df2334165293ea742da9fbb2e51f2739"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/48a570c964d8e37d353381e4195106277e17f5cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/57667eb7548faaac396c6e39f3b4444dab5b097c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a75c8f365e209aa9bb927b0942a7840152d44892"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c8dea7e7c6098e383e44f21a64d0431da5480e3f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d3677372e0275e139f0efd2872c5a524b5d12868"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f5802be65535f8818af7191159cf8c11f48ab2a2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T13:17:49Z"
  }
}