CVE-2026-49745 Graphics DDK vulnerability
Kernel software installed and running inside a Guest VM may post improper commands to the GPU Firmware to trigger a write of data outside the Guest's virtualised GPU memory. Software installed and run under a Guest VM can send commands to the GPU which result in out of bounds memory accesses. These can be used to escalate privileges.
Browse Linux security risksQuick answer
Imagination Technologies Graphics DDK should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 1.18 RTM2
- 23.2 RTM2
- 24.2 RTM2
- <= 25.3 RTM
- 26.1 RTM1
Fixed versions
- 26.1 RTM2
How to fix it
CVE-2026-49745 affects Graphics DDK and involves memory-safety failure. A crafted input may corrupt memory, crash the process, or enable code execution in the affected context. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade Graphics DDK to 26.1 RTM2 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Graphics DDK.
- Compare the installed version with the recorded affected range: 1.18 RTM2, 23.2 RTM2, 24.2 RTM2, <= 25.3 RTM, 26.1 RTM1.
- Upgrade Graphics DDK to 26.1 RTM2 or a later vendor-supported fixed release.
- Until patched, limit untrusted files and peers, apply resource limits, and isolate the affected parser or service.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Graphics DDK; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-49745 in place.
- Use a safe regression test to confirm the affected memory-safety failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-49745?
Imagination Technologies Graphics DDK versions listed as affected should be reviewed: 1.18 RTM2, 23.2 RTM2, 24.2 RTM2, <= 25.3 RTM, 26.1 RTM1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.