Public vulnerability disclosure

CVE-2026-15465

GPU DDK - Write UAF in OSDebugSignalPID due to incorrect management of PID resources

publishedCWE-416

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.

Technical severityUnscoredNo score in collected sources
Published2026-11-13Source updated 2026-11-13
Collected2026-11-131 attributed source

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Graphics DDK
Imagination Technologies
Platforms: Linux, Android
1.18 RTM2 (affected, custom)
23.2 RTM2 (affected, custom)
24.2 RTM2 (affected, custom)
25.1 RTM2 (affected, custom)
25.3 RTM (affected, custom)
26.1 RTM2 (affected, custom)
26.2 RTM (affected, custom)
26.3 RTM (unaffected, custom)
Other versions: unknown
CNA: imaginationtech

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide