Skip to content
statance
MenuClose
high · CVSS 7.8

CVE-2026-65584

GPU DDK - Stack Buffer Overflow via undersized UFO address array in DumpStalledContextInfo

Published 30 Oct 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-05 21:57 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

Software installed and run as a non-privileged user may conduct improper GPU system calls causing a stack overflow in the kernel. The overflow occurs when processing resolved Linux/Android fence synchronization checkpoints, while user checkpoints are excluded from the stack array. Successful exploitation can cause kernel memory corruption and typically results in a denial-of-service condition through a kernel crash.

The code vulnerability is a buffer write beyond the allocated array on the stack caused by copying excessive data from an internal buffer.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
Graphics DDKImagination Technologiesaffected: 1.18 RTM2; affected: 23.2 RTM2; affected: 24.2 RTM2; affected: 25.1 RTM2 to ≤ 25.3 RTM; affected: 26.1 RTM2; unaffected: 26.2 RTMSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed