CVE-2025-0031
BaseFortify
Publication date: 2026-02-10
Last updated on: 2026-02-10
Assigner: Advanced Micro Devices Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amd | epyc | From 1.37.2A (inc) |
| amd | epyc | From 1.37.31 (inc) |
| amd | epyc | to 1.0.0.F (inc) |
| amd | epyc | to 1.0.0.G (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
How can this vulnerability impact me? :
The impact of this vulnerability is primarily a potential loss of integrity. A malicious hypervisor exploiting this flaw could cause a migrated guest VM to run on an unintended CPU socket, which might compromise the integrity of the virtualized environment.
Can you explain this vulnerability to me?
This vulnerability is a use after free issue in the SEV firmware. It allows a malicious hypervisor to activate a migrated guest virtual machine with the SINGLE_SOCKET policy on a different CPU socket than the migration agent. This mismatch can potentially lead to a loss of integrity in the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know