# CVE-2020-6102: Memory corruption in AMD

> A memory corruption vulnerability in the AMD Radeon DirectX 11 driver allows attackers to execute arbitrary code on the Hyper-V host via a crafted shader file.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cv8v-qqh2-qx57

## What is CVE-2020-6102?

CVE-2020-6102 is a critical memory corruption vulnerability in AMD, published on 20 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.dll 26.20.15019.19000. An attacker can provide a a specially crafted shader file to trigger this vulnerability, resulting in code execution. This vulnerability can be triggered from a HYPER-V guest using the RemoteFX feature, leading to executing the vulnerable code on the HYPER-V host (inside of the rdvgm.exe process). Theoretically this vulnerability could be also triggered from web browser (using webGL and webassembly).

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-6102?

It affects 1 product.


Products: Amd Radeon Directx 11 Driver Atidxx64.dll.

## How do I fix CVE-2020-6102?

No fix has been published for CVE-2020-6102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-6102 being exploited?

There is no known exploitation of CVE-2020-6102 in the wild and no public exploit code.

## Other vulnerabilities in AMD

- [CVE-2020-6100](https://insights.sbomify.com/CVE-2020-6100/): Memory corruption in AMD (critical 9.9)
- [CVE-2020-6101](https://insights.sbomify.com/CVE-2020-6101/): Memory corruption in AMD (critical 9.9)
- [CVE-2020-6103](https://insights.sbomify.com/CVE-2020-6103/): Memory corruption in AMD (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6102 and fix it if it is affected.

What it is: CVE-2020-6102 is a critical memory corruption vulnerability in AMD, published on 20 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6102 in the wild and no public exploit code.

Affected product: AMD. 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-2020-6102/ (Markdown: https://insights.sbomify.com/CVE-2020-6102/index.md)
```

## Sources

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

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