AMI AptioV UEFI BIOS (SPI flash integrity verification): An actor with physical access can modify the SPI flash

Impact

An actor with physical access can modify the SPI flash without the modification being detected. The score is modest because it needs hands on the hardware, but the operator consequence is that your firmware integrity story has no floor: a node that passed through an untrusted physical environment can carry an undetectable implant. That matters concretely for GPU fleets in leased colo where remote hands are third-party staff, for hardware shipped internationally, for anything bought on the secondary market during a supply crunch, and for RMA units returning from a vendor depot.

Who can reach it

Physical access to the machine, no credentials needed. Anyone who can open the chassis and reach the SPI flash - datacenter remote-hands staff, shipping and logistics handling, a vendor's repair depot, or a hosting provider's own technicians.

What to do

BIOS update to BKC_5.37 or later - firmware flash plus reboot per node, vendor-rebase-gated. Because the threat model is physical rather than network, patching is only part of it: the process controls are what actually help. Take a firmware measurement baseline per node at commissioning, re-measure after any physical service event or RMA return, use chassis intrusion detection and seal logging, and treat any node that came back from third-party hands without a verified measurement as needing a reflash before it rejoins the pool.

References