AMD: Use After Free (CVE-2025-48521)
Published Sources: BSI, CVE.org, EUVD
What is affected, what to do
Improper input validation in the AMD Secure Processor (ASP) PCI driver could allow a local attacker to trigger a Use-After-Free (UAF) condition, potentially resulting in a loss of platform integrity or crash.
The available sources name no fixed version. Check the vendor guidance in the references below.
- Affected
- Google Cloud Platform
= Compute Engine..Compute Engine - AMD Prozessor
= EPYC..EPYC - AMD Prozessor
= Instinct MI300A..Instinct MI300A - AMD Prozessor
= Athlon..Athlon - AMD Prozessor
= Ryzen..Ryzen - open source Xen
= 4.17-4.21..4.17-4.21
- Google Cloud Platform
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.9
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v4
6.9
CVSS v4
Severity Medium on the scale from 0 to 10.
Source: BSI, CVE.org, EUVD
0.1 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 0.9
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 52.03 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.9 Methodology
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.9
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.1 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 0.9
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-416
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Improper input validation in the AMD Secure Processor (ASP) PCI driver could allow a local attacker to trigger a Use-After-Free (UAF) condition, potentially resulting in a loss of platform integrity or crash.
Source: BSI WID Portal, BSI CSAF, NVD (NIST), CVE.org (MITRE), cvelistv5, ENISA EUVD
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| AMD | AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics (formerly codenamed "Picasso") |
|
|
| AMD | AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Dali") |
|
|
| AMD | AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Picasso") |
|
|
| AMD | AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Pollock") |
|
|
| AMD | AMD EPYC™ 4004 Series Processors |
|
|
| AMD | AMD EPYC™ 4005 Series Processors |
|
|
| AMD | AMD EPYC™ Embedded 4004 Series Processors |
|
|
| AMD | AMD EPYC™ Embedded 4005 Series Processors |
|
|
| AMD | AMD EPYC™ Embedded 8004 Series Processors |
|
|
| AMD | AMD EPYC™ Embedded 9000 Series Processors |
|
|
| AMD | AMD Ryzen™ 3000 Series Desktop Processors (formerly codenamed "Matisse") |
|
|
| AMD | AMD Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Dali") |
|
|
| AMD | AMD Ryzen™ 4000 Series Desktop Processors (formerly codenamed "Renoir") |
|
|
| AMD | AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Renoir") |
|
|
| AMD | AMD Ryzen™ 5000 Series Desktop Processors (formerly codenamed "Vermeer") |
|
|
| AMD | AMD Ryzen™ 5000 Series Desktop Processors (formerly codenamed "Vermeer"/"Vermeer-X3D") |
|
|
| AMD | AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics (formerly codenamed "Cezanne") |
|
|
| AMD | AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Barcelo") |
|
|
| AMD | AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Cezanne") |
|
|
| AMD | AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Lucienne") |
|
|
| AMD | AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt") |
|
|
| AMD | AMD Ryzen™ 7000 Series Desktop Processors (formerly codenamed "Raphael"/"Raphael X3D") |
|
|
| AMD | AMD Ryzen™ 7000 Series Desktop Processors (formerly codenamed "Raphael"/"Raphael-X3D") |
|
|
| AMD | AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics (formerly codenamed "Mendocino") |
|
|
| AMD | AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Barcelo R") |
|
|
| AMD | AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R") |
|
|
| AMD | AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Phoenix") |
|
|
| AMD | AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Dragon Range") |
|
|
| AMD | AMD Ryzen™ 8000 Series Desktop Processors (formerly codenamed "Phoenix") |
|
|
| AMD | AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Hawk Point") |
|
|
| AMD | AMD Ryzen™ 9000 Series Desktop Processors (formerly codenamed "Granite Ridge") |
|
|
| AMD | AMD Ryzen™ AI 300 Series Processors (formerly codenamed "Strix Point") |
|
|
| AMD | AMD Ryzen™ Embedded 7000 Series Processors |
|
|
| AMD | AMD Ryzen™ Embedded 8000 Series Processors |
|
|
| AMD | AMD Ryzen™ Embedded 9000 Series Processors |
|
|
| AMD | AMD Ryzen™ Embedded R1000 Series Processors |
|
|
| AMD | AMD Ryzen™ Embedded R2000 Series Processors |
|
|
| AMD | AMD Ryzen™ Embedded V1000 Series Processors (formerly codenamed "Picasso") |
|
|
| AMD | AMD Ryzen™ Embedded V2000 Series Processors |
|
|
| AMD | AMD Ryzen™ Threadripper™ 3000 Processors (formerly codenamed "Castle Peak") |
|
|
| AMD | AMD Ryzen™ Threadripper™ 7000 Processors (formerly codenamed "Storm Peak") |
|
|
| AMD | AMD Ryzen™ Threadripper™ PRO 3000WX Processors (formerly codenamed "Castle Peak") |
|
|
| AMD | AMD Ryzen™ Threadripper™ PRO 5000 WX-Series Processors (formerly codenamed "Chagall") |
|
|
| AMD | AMD Ryzen™ Threadripper™ PRO 7000 WX-Series Processors (formerly codenamed "Storm Peak") |
|
|
| AMD | Prozessor |
|
|
Vendors and products
- AMD Amd Athlon™ 3000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "dali")
- AMD Amd Athlon™ 3000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "picasso")
- AMD Amd Epyc™ 4004 Series Processors
- AMD Amd Epyc™ 4005 Series Processors
- AMD Amd Epyc™ Embedded 4005 Series Processors
- AMD Amd Epyc™ Embedded 8004 Series Processors
- AMD Amd Ryzen™ 3000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "dali")
- AMD Amd Ryzen™ 4000 Series Desktop Processors (formerly Codenamed "renoir")
- AMD Amd Ryzen™ 4000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "renoir")
- AMD Amd Ryzen™ 5000 Series Desktop Processors With Radeon™ Graphics (formerly Codenamed "cezanne")
- AMD Amd Ryzen™ 5000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "barcelo")
- AMD Amd Ryzen™ 5000 Series Mobile Processors With Radeon™ Graphics (formerly Codenamed "cezanne")
Weakness classes (CWE)
CWE-416Use After Free
Variant
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Entry at MITRE CWE-416
References & sources
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2025-48521"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-48521.svg?lang=en" alt="CVE-2025-48521 – NEOSEC Intel" height="20"></a>