CVE-2025-62862
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ampere | ampereone_ac03 | 3.5.9.3 |
| ampere | ampereone_ac04 | 4.4.5.2 |
| ampere | ampereone_m | 5.4.5.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves an incorrectly formed Secure Monitor Call (SMC) to the UEFI-MM Boot Error Record Table driver on certain AmpereOne devices. It can cause either an out-of-bounds read, which leaks Secure-EL0 information to a process running in the Non-Secure state, or an out-of-bounds write, which can corrupt Secure or Non-Secure memory mapped to the UEFI-MM Secure Partition. The Secure Partition is designed for integrity rather than confidentiality, and the vulnerability affects the architectural separation between Secure and Non-Secure worlds. [2]
How can this vulnerability impact me? :
The out-of-bounds read could leak Secure-EL0 information to Non-Secure processes, though the confidentiality impact is negligible since no secrets or user data are processed in the UEFI-MM Secure Partition. The out-of-bounds write can corrupt Secure or Non-Secure memory, potentially leading to system hangs or privilege escalation. Overall, this could impact system stability and security by allowing local attackers with high privileges to escalate privileges or cause denial of service. [2]
What immediate steps should I take to mitigate this vulnerability?
Users should update their AmpereOne AC03 devices to version 3.5.9.3 or newer, AC04 devices to version 4.4.5.2 or newer, and AmpereOne M devices to version 5.4.5.1 or newer. Applying these updates will mitigate the vulnerability by fixing the incorrectly formed Secure Monitor Call (SMC) handling in the UEFI-MM Boot Error Record Table driver. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability involves leaking Secure-EL0 information to a Non-Secure process and potential memory corruption, but the confidentiality impact is negligible since no secrets or user data are processed in the UEFI-MM Secure Partition. Therefore, it is unlikely to directly affect compliance with standards like GDPR or HIPAA, which focus on protecting personal and sensitive data confidentiality. However, the potential for privilege escalation and system instability could indirectly impact compliance if exploited to gain unauthorized access or disrupt system operations. [2]