# CVE-2021-26365: Information disclosure in Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”

> Out-of-bounds reads in firmware headers allow attackers to leak memory contents or cause denial of service on AMD processors.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-49q9-hj6w-v395

## What is CVE-2021-26365?

CVE-2021-26365 is a high-severity vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain size values in firmware binary headers
could trigger out of bounds reads during signature validation, leading to
denial of service or potentially limited leakage of information about
out-of-bounds memory contents.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 54 products.


Products: Amd Amd 3015ce Firmware, Amd Amd 3015e Firmware, Amd Ryzen 3 2200g Firmware, Amd Ryzen 3 2200ge Firmware, Amd Ryzen 3 2200u Firmware, Amd Ryzen 3 2300u Firmware, Amd Ryzen 3 3200g Firmware, Amd Ryzen 3 3200ge Firmware, Amd Ryzen 3 3200u Firmware, Amd Ryzen 3 3250c Firmware, Amd Ryzen 3 3250u Firmware, Amd Ryzen 3 5300g Firmware, Amd Ryzen 3 5300ge Firmware, Amd Ryzen 3 5300u Firmware, Amd Ryzen 3 Pro 2100ge Firmware, Amd Ryzen 3 Pro 3200g Firmware, Amd Ryzen 3 Pro 3200ge Firmware, Amd Ryzen 5 2400g Firmware, Amd Ryzen 5 2400ge Firmware, Amd Ryzen 5 2500u Firmware and 34 more.

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

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

## Is CVE-2021-26365 being exploited?

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

## Other vulnerabilities in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”

- [CVE-2020-12930](https://insights.sbomify.com/CVE-2020-12930/): Privilege escalation in AMD Radeon RX 5000 Series & PRO W5000 Series (high 7.8)
- [CVE-2020-12931](https://insights.sbomify.com/CVE-2020-12931/): Privilege escalation in AMD Radeon RX 5000 Series & PRO W5000 Series (high 7.8)
- [CVE-2021-26392](https://insights.sbomify.com/CVE-2021-26392/): Memory corruption in AMD Radeon RX 5000 Series & PRO W5000 Series (high 7.8)
- [CVE-2021-26354](https://insights.sbomify.com/CVE-2021-26354/): Memory corruption in 2nd Gen AMD EPYC™ Processors (medium 5.5)
- [CVE-2021-26371](https://insights.sbomify.com/CVE-2021-26371/): Information disclosure in 1st Gen AMD EPYC™ Processors (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26365 is a high-severity vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26365 in the wild and no public exploit code.

Affected product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics   “Pollock”. 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-26365/ (Markdown: https://insights.sbomify.com/CVE-2021-26365/index.md)
```

## Sources

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

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