Skip to main content
VulnerabilityPublished

CVE-2026-21736: Imagination Technologies Graphics DDK · Improper Handling of Insufficient Permissions or Privileges

Affects Imagination Technologies Graphics DDKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.4 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Imagination TechnologiesGraphics DDKAffected
  • =1.17 RTM
  • =1.18 RTM
  • =23.2 RTM
  • ≥ 24.1 RTM, ≤ 25.1 RTM
Fixed in–

AI-suggested

To mitigate CVE-2026-21736, organizations should: 1) Monitor Imagination Technologies’ official channels for patches or updates addressing this vulnerability and apply them promptly once available. 2) Restrict local access to systems running affected versions of the Graphics DDK to trusted users only, minimizing the risk of local exploitation. 3) Employ application whitelisting and endpoint protection solutions to detect and prevent unauthorized execution of untrusted code that could attempt to exploit this flaw. 4) Use system-level security features such as SELinux or AppArmor to enforce strict access controls on GPU driver interfaces and memory resources. 5) Conduct regular security audits and memory integrity checks to detect anomalous behavior indicative of exploitation attempts. 6) For embedded or mobile device manufacturers using the affected DDK versions, consider firmware updates or hardware-based mitigations to isolate GPU memory access. These steps go beyond generic advice by focusing on access control, monitoring, and layered defense tailored to GPU driver vulnerabilities.

Description

Software installed and run as a non-privileged user may conduct improper GPU system calls to gain write permission to read-only wrapped user-mode memory. This is caused by improper handling of the memory protections for the user-mode wrapped memory resource.

References

Community reviews

Loading reviews…