Skip to content
Fencer Intel
critical 9.8

CVE-2025-62863 json

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 incorr…

published 10mo ago modified 27d ago also EUVD-2025-203818

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • amperecomputing ampereone_a192-32m_firmware 5.4.5.1
  • amperecomputing ampereone_a192-26m_firmware 5.4.5.1
  • amperecomputing ampereone_a160-28m_firmware 5.4.5.1
  • amperecomputing ampereone_a144-33m_firmware 5.4.5.1
  • amperecomputing ampereone_a144-26m_firmware 5.4.5.1
  • amperecomputing ampereone_a96-36m_firmware 5.4.5.1
  • amperecomputing ampereone_a96-36x_firmware 4.4.5.2
  • amperecomputing ampereone_a128-34x_firmware 4.4.5.2
  • amperecomputing ampereone_a144-24x_firmware 4.4.5.2
  • amperecomputing ampereone_a144-27x_firmware 4.4.5.2
  • amperecomputing ampereone_a160-28x_firmware 4.4.5.2
  • amperecomputing ampereone_a192-26x_firmware 3.5.9.3, 4.4.5.2
  • amperecomputing ampereone_a192-32x_firmware 3.5.9.3

Is CVE-2025-62863 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
10mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.