| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in AMD EPYC 9005 Processors, Ryzen AI 300 Processors, Ryzen 9000 Desktop Processors, Ryzen 9000HX Processors, Ryzen Al Max+, Ryzen Threadripper 9000 and EPYC Embedded 9000 Processors. It has been classified as problematic. This impacts an unknown function. Performing a manipulation results in cleanup. This vulnerability was named CVE-2025-0032. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in AMD EPYC 9005 Processors, Ryzen AI 300 Processors, Ryzen 9000 Desktop Processors, Ryzen 9000HX Processors, Ryzen Al Max+, Ryzen Threadripper 9000 and EPYC Embedded 9000 Processors. This affects an unknown code block. The manipulation with an unknown input leads to a cleanup vulnerability. CWE is classifying the issue as CWE-459. The product does not properly "clean up" and remove temporary or supporting resources after they have been used. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Improper cleanup in AMD CPU microcode patch loading could allow an attacker with local administrator privilege to load malicious CPU microcode, potentially resulting in loss of integrity of x86 instruction execution.
The advisory is shared at amd.com. This vulnerability is uniquely identified as CVE-2025-0032 since 11/21/2024. The exploitability is told to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-27086) and CERT Bund (WID-SEC-2025-1770). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Ubuntu Linux
- Oracle Linux
- Dell PowerEdge
- Lenovo Computer
- HP Computer
- AMD Prozessor
Product
Type
Vendor
Name
- EPYC 9005 Processors
- EPYC Embedded 9000 Processors
- Ryzen 9000 Desktop Processors
- Ryzen 9000HX Processors
- Ryzen AI 300 Processors
- Ryzen Al Max+
- Ryzen Threadripper 9000
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.9
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.2
CNA Vector (AMD): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: CleanupCWE: CWE-459
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
11/21/2024 CVE reserved09/06/2025 Advisory disclosed
09/06/2025 VulDB entry created
12/13/2025 VulDB entry last update
Sources
Advisory: amd.comStatus: Confirmed
CVE: CVE-2025-0032 (🔒)
GCVE (CVE): GCVE-0-2025-0032
GCVE (VulDB): GCVE-100-323013
EUVD: 🔒
CERT Bund: WID-SEC-2025-1770 - AMD Prozessoren: Mehrere Schwachstellen
Entry
Created: 09/06/2025 23:43Updated: 12/13/2025 18:23
Changes: 09/06/2025 23:43 (61), 09/07/2025 02:39 (1), 12/13/2025 18:23 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.