AMD EPYC 7003 Processors SEV Firmware use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.7$0-$5k0.00+

Summaryinfo

A vulnerability identified as problematic has been detected in AMD EPYC 7003 Processors, EPYC 7003 Embedded Processors, EPYC 8004 Processors, EPYC 8004 Embedded Processors, EPYC 8005 Processors, EPYC 8005 Embedded Processors, EPYC 9004 Processors, EPYC 9004 Embedded Processors, EPYC 9005 Processors and EPYC 9005 Embedded Processors. This affects an unknown function of the component SEV Firmware. This manipulation causes use after free. This vulnerability is tracked as CVE-2025-48504. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in AMD EPYC 7003 Processors, EPYC 7003 Embedded Processors, EPYC 8004 Processors, EPYC 8004 Embedded Processors, EPYC 8005 Processors, EPYC 8005 Embedded Processors, EPYC 9004 Processors, EPYC 9004 Embedded Processors, EPYC 9005 Processors and EPYC 9005 Embedded Processors. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the component SEV Firmware. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Operation on a resource after expiration or release in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to manipulate metadata pages potentially resulting in the loss of confidentiality and integrity of guest memory.

The advisory is shared at amd.com. This vulnerability is known as CVE-2025-48504 since 05/22/2025. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/10/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.7

VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/22/2025 CVE reserved
11/10/2026 +537 days Advisory disclosed
11/10/2026 +0 days VulDB entry created
11/10/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CNA: AMD
CVE: CVE-2025-48504 (🔒)

GCVE (CVE): GCVE-0-2025-48504
GCVE (VulDB): GCVE-100-435157

Entryinfo

Created: 11/10/2026 23:33
Changes: 11/10/2026 23:33 (63)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!