Description
Software installed and run as a non-privileged user may conduct improper GPU system calls to cause mismanagement of resources creating a write use after free scenario.



A shared resource (memory page) managed by a CPU thread of control (driver) and accessed by a GPU thread of control (Firmware) can cause a write UAF when the CPU thread frees the resource before the GPU FW has finished accessing it.
Published: 2026-06-19
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw occurs when the driver holds a control structure that includes a firmware address for a SYNC_PRIMITIVE_BLOCK but fails to keep a reference to that address. When the CPU thread frees the shared memory page before the GPU firmware has finished accessing it, the memory is reused. This write use‑after‑free situation can corrupt GPU state, potentially causing a crash or, if an attacker can influence the freed data, arbitrary code execution on the system. The vulnerability is classified as Use After Free (CWE‑416).

Affected Systems

Imagination Technologies Graphics DDK – no specific versions are listed in the CNA data.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, suggesting that explosive exploitation activity has not been observed yet. Nevertheless, the local attack vector is plausible: any non‑privileged user able to execute improper GPU system calls can trigger the condition. Because the flaw directly involves kernel‑space memory management for a GPU driver, the potential impact is high; service disruption or memory corruption could occur without additional privileges.

Generated by OpenCVE AI on June 19, 2026 at 10:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to the latest Imagination Technologies Graphics DDK that resolves the CCB memory reference issue.
  • If an upgrade is not immediately possible, restrict GPU usage to privileged users or disable GPU functionality that relies on the affected CCB mechanisms.
  • Enable kernel memory protection features, such as address‑space layout randomization and memory isolation, to reduce the impact of a write use‑after‑free in the driver code.

Generated by OpenCVE AI on June 19, 2026 at 10:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 19 Jun 2026 09:45:00 +0000

Type Values Removed Values Added
Description Software installed and run as a non-privileged user may conduct improper GPU system calls to cause mismanagement of resources creating a write use after free scenario. A shared resource (memory page) managed by a CPU thread of control (driver) and accessed by a GPU thread of control (Firmware) can cause a write UAF when the CPU thread frees the resource before the GPU FW has finished accessing it.
Title GPU DDK - kernel<->fw CCB contains SYNC_PRIMITIVE_BLOCK firmware address without holding reference
Weaknesses CWE-416
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: imaginationtech

Published:

Updated: 2026-06-19T09:28:53.868Z

Reserved: 2026-04-17T16:26:03.731Z

Link: CVE-2026-41156

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-19T10:30:15Z

Weaknesses