BadRAM

Am I affected by this bug?

While BadRAM may be possible on your system, it is primarily relevant in a cloud scenario with TEEs, where you inherently may not trust the cloud providers owning the systems. However, even in that scenario, there is no need to worry since we worked together with AMD to ensure appropriate countermeasures were developed that allow trusted firmware to detect BadRAM at boot time.

Does BadRAM need physical access; is this realistic?

BadRAM attacks require access to the SPD chip on the DIMM to modify its contents. This SPD chip can be exposed in several scenario's: Insider Threats in Cloud Environments In a cloud environment, employees of the cloud provider or local law enforcement could gain physical access to the hardware. These insiders could trivially modify the SPD chip to enable BadRAM attacks.

Should I update my system?

While it is good practice to keep your system up-to-date, there’s no immediate need for individual users to update their systems. At this time, most cloud providers will have updated their firmware to include the countermeasures provided by AMD.

What is the impact of BadRAM; isn't the memory encrypted anyway?

BadRAM can circumvent critical CPU-based memory isolation features based on physical address checks, which has significant consequences for TEEs like AMD SEV-SNP. While TEEs commonly encrypt data in memory, this encryption is static, meaning that the same plaintext always maps to the same ciphertext. This can prevent threats like cold boot attacks, but is not a significant roadblock for BadRAM.

How is this different from cold boot attacks?

Cold boot attacks exploit the residual data in DRAM by quickly restarting or transferring memory modules to extract secret data. These attacks can nowadays easily be mitigated by enabling full memory encryption, whereas this is not a big hurdle for BadRAM. BadRAM is also a more powerful attack, it is not only able to observe the memory at any given point, but can also actively modify or replay data.