# CVE-2023-4969: GPU kernel implementations susceptible to memory leak

> Attackers can read sensitive data from other GPU kernels via local memory, affecting OS-level GPU drivers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** DEBIAN-CVE-2023-4969, GHSA-95ph-5wpx-w6gq, UBUNTU-CVE-2023-4969

## What is CVE-2023-4969?

CVE-2023-4969 is a medium-severity vulnerability in Khronos Group OpenCL, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A GPU kernel can read sensitive data from another GPU kernel (even from another user or app) through an optimized GPU memory region called _local memory_ on various architectures.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2023-4969?

It affects 132 products.


Products: Amd Athlon 3000g Firmware, Amd Instinct Mi100 Firmware, Amd Instinct Mi210 Firmware, Amd Instinct Mi250 Firmware, Amd Instinct Mi300a Firmware, Amd Instinct Mi300x Firmware, Amd Radeon Instinct Mi25 Firmware, Amd Radeon Instinct Mi50 Firmware, Amd Radeon Pro V520 Firmware, Amd Radeon Pro V620 Firmware, Amd Radeon Pro W5500x Firmware, Amd Radeon Pro W5700x Firmware, Amd Radeon Pro W6300m Firmware, Amd Radeon Pro W6400 Firmware, Amd Radeon Pro W6500m Firmware, Amd Radeon Pro W7500 Firmware, Amd Radeon Pro W7600 Firmware, Amd Radeon Rx 5300 Firmware, Amd Radeon Rx 5300m Firmware, Amd Radeon Rx 5300xt Firmware and 112 more.

## How do I fix CVE-2023-4969?

Apply the vendor's patch.

## Is CVE-2023-4969 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4969 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4969 and fix it if it is affected.

What it is: CVE-2023-4969 is a medium-severity vulnerability in Khronos Group OpenCL, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4969 exists.

Affected product: Khronos Group OpenCL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4969/ (Markdown: https://insights.sbomify.com/CVE-2023-4969/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4969
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4969
- OSV: https://osv.dev/vulnerability/CVE-2023-4969

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4969/
Summaries are generated and may contain mistakes; the official description above is the record.