AMD EPYC Embedded Processors/EPYC Processors Ring Buffer Queue Status Page input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as very critical, has been found in AMD EPYC Embedded Processors and EPYC Processors. This issue affects some unknown processing of the component Ring Buffer Queue Status Page. The manipulation leads to input validation. This vulnerability is referenced as CVE-2025-62620. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in AMD EPYC Embedded Processors and EPYC Processors (affected version unknown) and classified as very critical. This issue affects an unknown functionality of the component Ring Buffer Queue Status Page. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Improper validation of unsafe equivalence in input could allow an attacker with high privileges to reclaim the ring buffer queue status page, potentially resulting in loss of guest memory integrity.
The advisory is shared at amd.com. The identification of this vulnerability is CVE-2025-62620 since 10/16/2025. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 9.1VulDB Meta Temp Score: 9.1
VulDB Base Score: 9.1
VulDB Temp Score: 9.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/16/2025 CVE reserved11/10/2026 Advisory disclosed
11/10/2026 VulDB entry created
11/10/2026 VulDB entry last update
Sources
Advisory: amd.comStatus: Confirmed
CNA: AMD
CVE: CVE-2025-62620 (🔒)
GCVE (CVE): GCVE-0-2025-62620
GCVE (VulDB): GCVE-100-435065
Entry
Created: 11/10/2026 23:14Changes: 11/10/2026 23:14 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.