Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62863: n/a

0
Critical
VulnerabilityCVE-2025-62863cvecve-2025-62863
Published: Tue Dec 16 2025 (12/16/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

Ampere AmpereOne AC03 devices before 3.5.9.3, AmpereOne AC04 devices before 4.4.5.2, and AmpereOne M devices before 5.4.5.1 allow an incorrectly formed SMC call to UEFI-MM PCIe driver that could result in an out-of-bounds write within PCIe driver’s S-EL0 address space.

AI-Powered Analysis

AILast updated: 12/16/2025, 17:59:54 UTC

Technical Analysis

CVE-2025-62863 is a firmware vulnerability identified in Ampere AmpereOne AC03, AC04, and M devices, specifically in versions before 3.5.9.3, 4.4.5.2, and 5.4.5.1 respectively. The vulnerability stems from an incorrectly formed Secure Monitor Call (SMC) to the Unified Extensible Firmware Interface - Management Mode (UEFI-MM) PCIe driver. This malformed call can trigger an out-of-bounds write operation within the PCIe driver's S-EL0 (Secure EL0) address space, which is a privileged memory region used by the PCIe driver for secure operations. Out-of-bounds writes are a form of memory corruption that can lead to unpredictable behavior, including potential escalation of privileges, arbitrary code execution, or system crashes (denial of service). The vulnerability affects the firmware layer, which is critical for initializing hardware and establishing a trusted execution environment. Exploitation would likely require local access or the ability to invoke SMC calls, but no user interaction is explicitly required once access is obtained. The absence of a CVSS score suggests the vulnerability is newly disclosed and pending formal scoring. No public exploits have been reported, indicating limited or no active exploitation at this time. The affected devices are used in server and cloud infrastructure environments, where PCIe devices are common for high-performance computing and networking. The vulnerability's impact is significant due to the potential compromise of system integrity at a low-level firmware component.

Potential Impact

For European organizations, the impact of CVE-2025-62863 could be substantial, especially for those relying on AmpereOne AC03, AC04, or M devices in data centers, cloud services, or critical infrastructure. An out-of-bounds write in the PCIe driver's secure memory space could lead to system instability, crashes, or unauthorized code execution, potentially allowing attackers to bypass security controls or disrupt services. This could affect confidentiality, integrity, and availability of systems, leading to data breaches, service outages, or compromised workloads. Given the firmware-level nature of the vulnerability, remediation is complex and requires firmware updates, which may involve planned downtime and coordination with hardware vendors. Organizations in sectors such as finance, telecommunications, government, and cloud service providers are particularly at risk due to their reliance on secure and stable server hardware. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability details are widely known.

Mitigation Recommendations

To mitigate CVE-2025-62863, European organizations should: 1) Identify all AmpereOne AC03, AC04, and M devices in their environment and verify firmware versions. 2) Coordinate with Ampere or authorized vendors to obtain and apply firmware updates to versions 3.5.9.3 or later for AC03, 4.4.5.2 or later for AC04, and 5.4.5.1 or later for M devices. 3) Schedule firmware upgrades during maintenance windows to minimize operational impact. 4) Implement strict access controls to limit the ability to invoke SMC calls, restricting local administrative access to trusted personnel only. 5) Monitor system logs and PCIe driver activity for anomalies that could indicate exploitation attempts. 6) Incorporate firmware integrity checks and secure boot mechanisms to detect unauthorized firmware modifications. 7) Engage with hardware vendors for ongoing security advisories and patches. 8) Consider network segmentation and isolation of critical systems using affected hardware to reduce attack surface. These steps go beyond generic patching by emphasizing access control, monitoring, and operational planning.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-10-24T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 694194749050fe850806087a

Added to database: 12/16/2025, 5:18:44 PM

Last enriched: 12/16/2025, 5:59:54 PM

Last updated: 12/18/2025, 4:52:51 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats