Ampereone A96 36M Firmware
Monthly
An out-of-bounds write in the UEFI-MM Secure Partition of Ampere AmpereOne platform firmware can be triggered by a malformed SMC (Secure Monitor Call) issued to the MMCommunicate service, allowing memory corruption inside the secure partition context on affected devices running firmware earlier than AC03 3.5.9.3, AC04 4.4.5.2, or AmpereOne M 5.4.5.1. Although the NVD-published CVSS 3.1 vector scores this 9.8 with AV:N/PR:N, that rating does not match the attack surface: the MMCommunicate SMC interface is a local, privileged interface, and our independent assessment reassesses the flaw as CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, meaning an attacker must already hold OS kernel/EL1-level execution on the host before reaching the vulnerable code. There is no indication of active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so real-world risk is gated behind a prior operating-system compromise rather than direct remote reachability. Full technical details and fixed firmware versions are published by the vendor in advisory AMP-SB-0007.
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.
Incorrectly formed SMC (Secure Monitor Call) instructions against the UEFI-MM Boot Error Record Table driver on Ampere AmpereOne AC03, AC04, and M devices running unpatched firmware can trigger memory corruption inside the UEFI-MM Secure Partition. An attacker must already hold high-privilege Non-Secure execution at EL1 (OS kernel level) to issue the call, meaning this is a local, PR:H issue rather than a remote or unprivileged-user attack, and exposure is bounded by what the Secure Partition Manager has mapped to the UEFI-MM partition. The result can be an out-of-bounds read that leaks Secure-EL0 data into the Non-Secure world, or an out-of-bounds write that corrupts Secure or Non-Secure memory; EPSS is negligible (0.12%, 2nd percentile), no KEV listing applies, and no public exploit has been identified at time of analysis.
An out-of-bounds write in the UEFI-MM Secure Partition of Ampere AmpereOne platform firmware can be triggered by a malformed SMC (Secure Monitor Call) issued to the MMCommunicate service, allowing memory corruption inside the secure partition context on affected devices running firmware earlier than AC03 3.5.9.3, AC04 4.4.5.2, or AmpereOne M 5.4.5.1. Although the NVD-published CVSS 3.1 vector scores this 9.8 with AV:N/PR:N, that rating does not match the attack surface: the MMCommunicate SMC interface is a local, privileged interface, and our independent assessment reassesses the flaw as CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, meaning an attacker must already hold OS kernel/EL1-level execution on the host before reaching the vulnerable code. There is no indication of active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, so real-world risk is gated behind a prior operating-system compromise rather than direct remote reachability. Full technical details and fixed firmware versions are published by the vendor in advisory AMP-SB-0007.
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.
Incorrectly formed SMC (Secure Monitor Call) instructions against the UEFI-MM Boot Error Record Table driver on Ampere AmpereOne AC03, AC04, and M devices running unpatched firmware can trigger memory corruption inside the UEFI-MM Secure Partition. An attacker must already hold high-privilege Non-Secure execution at EL1 (OS kernel level) to issue the call, meaning this is a local, PR:H issue rather than a remote or unprivileged-user attack, and exposure is bounded by what the Secure Partition Manager has mapped to the UEFI-MM partition. The result can be an out-of-bounds read that leaks Secure-EL0 data into the Non-Secure world, or an out-of-bounds write that corrupts Secure or Non-Secure memory; EPSS is negligible (0.12%, 2nd percentile), no KEV listing applies, and no public exploit has been identified at time of analysis.