Skip to main content
VulnerabilityPublished Updated

CVE-2026-22163: Imagination Technologies Graphics DDK · Missing Synchronization

Affects Imagination Technologies Graphics DDKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 1 Nov 2026, 11:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 1 Nov 2026.

What to do

Affected software

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

AI-suggested

  1. Restrict access to the Graphics DDK kernel module IOCTL interface to trusted and authenticated processes only, minimizing the attack surface.
  2. Employ strict privilege separation and ensure that only necessary processes run with low-level privileges capable of interacting with the GPU driver.
  3. Monitor and audit kernel module interactions for unusual or unsupported IOCTL calls that may indicate exploitation attempts.
  4. Implement kernel-level integrity monitoring to detect unauthorized memory writes or modifications.
  5. Coordinate with Imagination Technologies for timely patches and updates; prioritize deployment of fixes once available.
  6. For embedded and mobile device manufacturers, consider firmware updates that include patched DDK versions and enhanced access controls.
  7. Use hardware-based security features such as IOMMU to restrict device access to physical memory regions, limiting the impact of arbitrary writes.
  8. Conduct thorough security testing of GPU driver interfaces during development to detect synchronization issues and race conditions.
  9. Educate system administrators and developers about the risks of unsynchronized shared resource access in kernel modules to prevent similar vulnerabilities.

Description

Requires malware code to misuse the DDK kernel module IOCTL interface. Such code can use the interface in an unsupported way that allows subversion of the GPU to perform writes to arbitrary physical memory pages. The product utilises a shared resource in a concurrent manner but does not attempt to synchronise access to the resource.

References

Community reviews

Loading reviews…