# CVE-2021-26410: Information disclosure in AMD Radeon™ PRO V520

> An attacker can infer kernel memory contents via improper syscall validation in the AMD Secure Processor, leading to information disclosure.

- **Severity:** Low 1.8 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-58jp-cg46-mwcw

## What is CVE-2021-26410?

CVE-2021-26410 is a low-severity vulnerability in AMD Radeon™ PRO V520, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter values from its own memory space allowing an attacker to infer the contents of the kernel memory leading to potential information disclosure.

Weakness: CWE-822 (Untrusted Pointer Dereference)

## Which versions are affected by CVE-2021-26410?


## How do I fix CVE-2021-26410?

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

## Is CVE-2021-26410 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26410 and fix it if it is affected.

What it is: CVE-2021-26410 is a low-severity vulnerability in AMD Radeon™ PRO V520, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26410 in the wild and no public exploit code.

Affected product: AMD Radeon™ PRO V520. 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-2021-26410/ (Markdown: https://insights.sbomify.com/CVE-2021-26410/index.md)
```

## Sources

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

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