Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain kernel-level execution on host OS
  2. Delivery
    Craft malformed SMC call to UEFI-MM
  3. Exploit
    Trigger out-of-bounds write in S-EL0 PCIe driver
  4. Execution
    Corrupt secure-world firmware memory
  5. Impact
    Escalate into secure firmware trust domain

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the ability to issue a (malformed) SMC call to the UEFI-MM PCIe driver - an operation only available to code executing at the normal-world OS kernel/hypervisor privilege level (EL1+) on AArch64, since SMC is a privileged instruction. The attacker must therefore already hold kernel-level control on an affected AmpereOne AC03/AC04/M server running firmware below the fixed versions; this is not reachable by an unauthenticated remote user despite the input's AV:N rating. The limiting factors are the mandatory pre-existing privileged execution context and the requirement to run on specific unpatched AmpereOne firmware revisions.

Impact

The input assigns CVSS 9.8 with vector AV:N/AC:L/PR:N/UI:N, which treats this as a remote, unauthenticated, network-reachable flaw - but that rating conflicts directly with the technical description. The vulnerability is triggered by an 'incorrectly formed SMC call' to the UEFI-MM (Management Mode) PCIe driver, and SMC (Secure Monitor Call) instructions can only be issued by code already running at the OS kernel level (EL1) or higher on the ARM AArch64 platform. This means a network-only, zero-privilege attacker almost certainly CANNOT reach this code path directly; realistic exploitation presupposes prior privileged (kernel/hypervisor-level) code execution in the normal world. Therefore the AV:N/PR:N portion of the input CVSS appears materially overstated - verify with Ampere advisory AMP-SB-0007. On other signals: there is no CISA KEV listing and no public exploit identified, so there is no evidence of active exploitation or weaponization. The genuine concern is high technical impact (out-of-bounds write in secure S-EL0 address space, enabling a trust-boundary crossing from the normal world into secure firmware), not ease of initial access. Net assessment: this is a high-severity firmware/secure-world privilege-escalation primitive rather than the internet-facing, trivially-exploitable 9.8 the headline score implies; priority is real for affected Ampere server fleets but should be weighted by the local-privilege prerequisite.

Exploit ScenarioDerived

An attacker who has already achieved kernel-level code execution on an AmpereOne server (for example via a prior OS/hypervisor compromise or a malicious privileged tenant) issues a malformed SMC call to the UEFI-MM PCIe driver, triggering an out-of-bounds write inside the driver's secure S-EL0 address space. By controlling the corrupted secure-world memory, the attacker escalates from normal-world privilege into the firmware trust domain, undermining platform/secure-boot integrity. No public proof-of-concept is currently identified, and the SMC-based trigger implies low complexity once the required privilege level is held.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

An out-of-bounds write in the UEFI-MM PCIe driver of Ampere AmpereOne server firmware lets code that already holds kernel- or hypervisor-level control (EL1 and above on AArch64) corrupt memory inside the driver's S-EL0 secure-partition address space by issuing a malformed SMC call. Only systems running AmpereOne AC03 firmware below 3.5.9.3, AC04 below 4.4.5.2, or AmpereOne M below 5.4.5.1 are affected. Although the input scores this 9.8 with a AV:N/PR:N vector, the SMC instruction is privileged and cannot be reached by an unauthenticated remote user; the practical precondition is pre-existing privileged execution on the host (assessed CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, and it is not listed in CISA KEV; vendor firmware fixes are available.

RemediationAI

Upgrade the affected platform firmware to the fixed release for the relevant generation: AmpereOne AC03 to 3.5.9.3 or later, AmpereOne AC04 to 4.4.5.2 or later, and AmpereOne M to 5.4.5.1 or later (vendor firmware patch; details in AMP-SB-0007 at https://amperecomputing.com/products/security-bulletins/amp-sb-0007 and the product security page https://amperecomputing.com/products/product-security). Because exploitation requires the ability to execute the privileged SMC instruction from normal-world EL1+ code, there is no external network-facing attack surface to close with a firewall rule; the practical compensating controls are strict host/hypervisor hardening - keep OS kernels, hypervisors and any co-resident tenants fully patched and distrust workloads that could already run privileged guest or host code, since a compromise at that layer is a prerequisite rather than a consequence of this bug. Operators who cannot immediately apply firmware updates should treat kernel-level compromise on these hosts as a path to secure-partition memory corruption, isolate tenants so untrusted code never reaches EL1/hypervisor privileges, and schedule the firmware update regardless, noting that firmware flashing typically requires a maintenance window and a reboot of the server.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a memory-safety defect (CWE-787, out-of-bounds write) in the UEFI-MM PCIe driver shipped in Ampere AmpereOne system firmware. On AArch64, an SMC (Secure Monitor Call) is the architectural instruction used by normal-world code to request services from the secure monitor at EL3, which in this design dispatches to the PCIe driver executing in a secure partition's S-EL0 context. Because the driver validates the parameters of the incoming call incorrectly, a malformed request causes it to write past the end of a buffer inside its own S-EL0 address space, not in the normal-world kernel's memory. Reaching this code path requires executing a privileged SMC instruction, so the attacker must already control normal-world code at EL1 (OS kernel) or above - a remote, unauthenticated network attacker cannot trigger it. The affected CPEs cover the AmpereOne AC03/AC04/M product family firmware images (A96-36M/36X, A128-34X, A144-24X/26M/27X/33M, A160-28M, A192-26M/32M and related SKUs), confirming that the flaw lives in the platform firmware rather than in a user-space component.

Know when Ampereone A192 32M Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.2 HIGH

SMC calls require kernel-level privilege (AV:L, PR:H); the write crosses from normal world into the secure S-EL0 firmware domain (S:C) with full C/I/A impact there.

3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Ampere AmpereOne server firmware contains a critical out-of-bounds write in the UEFI-MM PCIe driver that can corrupt memory inside the driver's S-EL0 secure-partition address space. The vulnerability cannot be reached by an unauthenticated remote attacker: exploitation requires an adversary who already holds kernel- or hypervisor-level (EL1 and above) control on the host, so its primary effect is to deepen the damage an already-privileged intruder can inflict rather than to open a new entry point. Leadership should care because AmpereOne platforms commonly host multi-tenant and confidential-computing workloads whose isolation guarantees could be undermined, and because remediation requires coordinated firmware maintenance across the server fleet.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 72% exploitable
Prevalence
Low
niche datacenter ARM server CPU, limited-vendor hyperscaler/enterprise footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Affected Products (CPE)CVE.org

cpe:2.3:o:amperecomputing:ampereone_a192-32m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a192-26m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a160-28m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a144-33m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a144-26m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a96-36m_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a96-36x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a128-34x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a144-24x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a144-27x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a160-28x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a192-26x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a192-26x_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:amperecomputing:ampereone_a192-32x_firmware:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy