AMI AptioV BIOS (out-of-bounds write): Local out-of-bounds write in firmware causing data corruption and loss

Impact

Local out-of-bounds write in firmware causing data corruption and loss of availability.

Who can reach it

Local low-privilege access.

What to do

AMI ships the fix to OEMs, not to you - obtain the updated BIOS from your board/server vendor (Supermicro, Gigabyte, ASRock Rack, Quanta, Tyan etc.) and flash it. Expect a lag of weeks to months between the AMI advisory and an OEM image for your exact SKU, and expect some SKUs never to get one. Cold reboot per node.

References

Related entries

• AMI AptioV BIOS (out-of-bounds write): Second local out-of-bounds write in the same AptioV advisoryCVE-2025-22831 · AMI AptioV BIOS (out-of-bounds write)High
• Dell iDRAC Tools (improper access control): A low-privileged local attacker escalates privileges through the iDRACCVE-2025-27689 · Dell iDRAC Tools (improper access control)High
• AMI AptioV BIOS (out-of-bounds memory operation): Local attacker causes firmware memory corruption impacting integrityCVE-2025-33044 · AMI AptioV BIOS (out-of-bounds memory operation)High
• Linux bnxt_en driver (ethtool coredump / bnxt_get_coredump): Out-of-bounds memcpy when retrieving a firmware coredumpCVE-2025-37911 · Linux bnxt_en driver (ethtool coredump / bnxt_get_coredump)High
• Linux kernel Soft-RoCE completion queue (rdma_rxe, rxe_cq_cleanup on create failure): Syzkaller-found slabCVE-2025-38024 · Linux kernel Soft-RoCE completion queue (rdma_rxe, rxe_cq_cleanup on create failure)High
• Linux KVM/SVM - SEV/SEV-ES intra-host migration during vCPU creation: KVM permitted SEV/SEV-ES intra-host migrationCVE-2025-38455 · Linux KVM/SVM - SEV/SEV-ES intra-host migration during vCPU creationHigh