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

> A transient execution flaw in AMD processors allows local attackers to infer control registers, bypassing UMIP protections to leak sensitive information.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/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:** 8 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-36348, GHSA-hj5p-w9cq-q437

## What is CVE-2024-36348?

CVE-2024-36348 is a low-severity vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, published on 8 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively even if UMIP feature is enabled, potentially resulting in information leakage.

Weakness: CWE-1420 (Exposure of Sensitive Information during Transient Execution)

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


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

Apply the vendor's patch.

## Is CVE-2024-36348 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36348 is a low-severity vulnerability in AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, published on 8 Jul 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-36348 in the wild and no public exploit code.

Affected product: AMD Athlon™ 3000 Series Desktop 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-36348/ (Markdown: https://insights.sbomify.com/CVE-2024-36348/index.md)
```

## Sources

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

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