CVE-2025-62863
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAmpere 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an out-of-bounds write vulnerability in the UEFI-MM (UEFI Management Mode) PCIe driver on AmpereOne processors. An attacker can exploit an incorrectly formed SMC (Secure Monitor Call) to trigger an out-of-bounds write within the PCIe driver's S-EL0 (Secure EL0) address space, potentially achieving code execution at the secure firmware level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.4.5.1< 5.4.5.1< 5.4.5.1< 5.4.5.1< 5.4.5.1< 5.4.5.1< 4.4.5.2< 4.4.5.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AmpereOne processor modelRun `dmidecode -t processor | grep -i 'product name'` or check BMC/IPMI for processor information. Look for model numbers such as A192, A160, A144, A96, or A128.Affected if Processor is an AmpereOne model (A192, A160, A144, A96, or A128) from the affected product list.
-
Retrieve UEFI firmware versionCheck firmware version via `dmidecode -s bios-version`, or access BMC/IPMI web interface or CLI (e.g., `ipmi chassis status` or vendor-specific tools), or view in UEFI/BIOS setup screen under firmware/bios information.Affected if Unable to retrieve a firmware version, or version is blank/unknown.
-
Compare firmware version against affected rangesBased on your specific AmpereOne model from step 1, compare your firmware version to: A192 32m/26m, A160 28m, A144 33m/26m, A96 36m: version < 5.4.5.1; A96 36x: version < 4.4.5.2; A128 34x: version < 4.4.5.2.Affected if Installed firmware version is lower than the version threshold for your specific model.
-
Confirm Management Mode (MM) PCIe driver is presentThis is a UEFI-MM component. Check system firmware/UEFI logs or documentation for presence of Management Mode PCIe driver functionality. This is typically enabled by default on affected AmpereOne systems.Affected if System uses UEFI-MM (Management Mode) for PCIe operations, which is standard on AmpereOne firmware.
You are affected if your AmpereOne processor runs firmware version lower than 5.4.5.1 (for A192, A160, A144, A96 36m), 4.4.5.2 (for A96 36x and A128 34x), and your system has the UEFI-MM PCIe driver enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.4.5.25.4.5.1
Apply vendor firmware updates: upgrade AmpereOne AC03 to version 3.5.9.3 or later, AC04 to 4.4.5.2 or later, and M series to 5.4.5.1 or later. If patching is not immediately feasible, restrict physical access and reduce attack surface by disabling unnecessary PCIe functions.
AmpereOne M (A192, A160, A144, A96 36m): firmware >= 5.4.5.1 | AmpereOne AC04 (A96 36x, A128 34x): firmware >= 4.4.5.2
- 1. Identify the exact AmpereOne processor model (A192, A160, A144, A96, or A128) and variant (e.g., 32m, 26m, 28m, 33m, 36m, 36x, 34x) in the affected system
- 2. Check the current firmware version installed on the system
- 3. For AmpereOne A96 36x and A128 34x systems: upgrade firmware to version 4.4.5.2 or later
- 4. For all other affected models (A192 32m, A192 26m, A160 28m, A144 33m, A144 26m, A96 36m): upgrade firmware to version 5.4.5.1 or later
- 5. Verify the firmware upgrade was successful by confirming the new version is installed
- 6. Test that the system boots normally and operates without issues after the firmware update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62863 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62863 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data