# CVE-2024-36353: Information disclosure in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics

> A malicious process can read leftover GPU memory values due to insufficient clearing, potentially exposing sensitive data.

- **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:** No
- **Published:** 2 Mar 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-hwg4-5cx4-h25m

## What is CVE-2024-36353?

CVE-2024-36353 is a medium-severity vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics, published on 2 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient clearing of GPU global memory could allow a malicious process running on the same GPU to read left over memory values potentially leading to loss of confidentiality.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2024-36353?


## How do I fix CVE-2024-36353?

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

## Is CVE-2024-36353 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36353 and fix it if it is affected.

What it is: CVE-2024-36353 is a medium-severity vulnerability in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics, published on 2 Mar 2025. 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-2024-36353 in the wild and no public exploit code.

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

## Sources

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

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