Skip to main content
No exploitation reportedFix available

CVE-2026-65586

GPU DDK - Write UAF due to missing cleanup reference for abort command submitted via PVRSRVRGXKickTA3DKM

No exploitation reported by the sources we read.

  • Published2026-10-30
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Software installed and run as a non-privileged user may conduct improper GPU system calls to free memory in still in use, replace with another allocation and cause arbitrary memory reads or writes to physical memory pages. A memory buffer managed by a CPU thread of control (driver) and accessed by a GPU thread of control (firmware) can be freed while in use. Software installed and run as a non-privileged user may replace that buffer with another and replace a shared resource (memory page address list) managed by the CPU thread of control (driver) leading to the GPU accessing memory not managed by the CPU thread of control (driver).

Timeline

dates in UTC
  1. 2026-10-3001:42CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As imaginationtech, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Imagination Technologies Graphics DDKother versions: unknown

    platforms: Linux, Android

    Affected
    • = 1.18 RTM2no fix statedcustom
    • = 23.2 RTM2no fix statedcustom
    • = 24.2 RTM2no fix statedcustom
    • ≥ 25.1 RTM2, ≤ 25.3 RTMno fix statedcustom
    • = 26.1 RTM2no fix statedcustom

    Not affected = 26.2 RTM

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • :unknown:Androidfrom SoCVersion:0 · fixed in SoCVersion:2026-11-05

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Published
2026-10-30
Last Modified
2026-11-05
NVD status
Deferred
GitHub Advisory
GHSA-8pw8-g8hf-x6v7

Frequently asked questions

What is CVE-2026-65586?

Software installed and run as a non-privileged user may conduct improper GPU system calls to free memory in still in use, replace with another allocation and cause arbitrary memory reads or writes to physical memory pages. A memory buffer managed by a CPU thread of control (driver) and accessed by a GPU thread of control (firmware) can be freed while in use. Software installed and run as a non-privileged user may replace that buffer with another and replace a shared resource (memory page address list) managed by the CPU thread of control (driver) leading to the GPU accessing memory not managed by the CPU thread of control (driver).

Is CVE-2026-65586 actively exploited?

Active exploitation of CVE-2026-65586 has not been confirmed. Its EPSS score was 0.1% on 2026-11-05, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-65586?

CVE-2026-65586 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.

Running :unknown:? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record