AMI AptioV BIOS: buffer access with incorrect length value allows local code execution in firmware

CVSS 8.3CVE-2025-58774Firmware, BMC & network fabriccurated

Impact

A local user on the server can drive a BIOS code path that reads or writes a buffer using an incorrect length, corrupting firmware memory and executing arbitrary code at firmware privilege. AptioV is the UEFI base that many server OEMs build on, so this is a platform-level exposure on whatever portion of a GPU fleet ships that BIOS lineage. Code running below the OS sits beneath hypervisor and kernel isolation, which makes it a credible persistence and platform-integrity problem rather than only a crash. The advisory also records an availability impact, so the realistic worst case on a GPU node is a host left unbootable until the platform is reflashed or re-provisioned.

Who can reach it

Local access to the machine with low privileges required (CVSS vector states AV:L/PR:L, no user interaction). No network or management-VLAN path is described in the record.

What to do

Identify whether your server BIOS derives from AMI AptioV and obtain a fixed BIOS build from the server OEM, not from AMI directly - AMI advisory AMI-SA-2026002 is the upstream reference and the fix reaches operators as an OEM BIOS release. Remediation is a BIOS flash, so each affected node must be drained, taken out of service, flashed and rebooted; there is no live mitigation. The record names no fixed version, so treat the OEM's BIOS release notes as the authority on which build carries the fix.

References

https://nvd.nist.gov/vuln/detail/CVE-2025-58774 https://go.ami.com/hubfs/Security%20Advisories/2026/AMI-SA-2026002.pdf

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.