CVE intelligence and bounded remediation

CVE-2025-62862 — Amperecomputing Ampereone A192-32M Firmware security vulnerability

Medium CVSS 4.6

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 Boot Error Record Table driver that could result in (1) an out-of-bounds read which leaks Secure-EL0 information to a process running in Non-Secure state or (2) an out-of-bounds write which corrupts Secure or Non-Secure memory, limited to memory mapped to UEFI-MM Secure Partition by the Secure Partition Manager.

Severity
Medium
CVSS
4.6 (3.1)
Published
2025-12-16
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-125, CWE-787

Affected products

  • amperecomputing / ampereone_a192-32m_firmware
  • amperecomputing / ampereone_a192-26m_firmware
  • amperecomputing / ampereone_a160-28m_firmware
  • amperecomputing / ampereone_a144-33m_firmware
  • amperecomputing / ampereone_a144-26m_firmware
  • amperecomputing / ampereone_a96-36m_firmware

Showing 6 representative product identities from 14 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.