May 17, 2026
Infinity Flub, Trust Wreck
Fabricked: Misconfiguring Infinity Fabric to Break AMD SEV-SNP
Researchers say AMD’s cloud privacy shield can be fooled, and commenters are not shocked
TLDR: Researchers say AMD’s cloud privacy system can be undermined by a malicious server operator during startup, letting them read protected data. Commenters split between “this proves confidential computing is a fantasy” and “there’s already a fix, and the attack needs a very bad host anyway.”
A fresh security paper dropped a very uncomfortable claim: AMD’s much-hyped privacy feature for cloud servers can be broken if a malicious host sets the machine up wrong from the start. In plain English, the protection is supposed to keep your rented cloud computer private even from the company running it. But the researchers say a bad actor controlling the server’s startup software can quietly reroute memory traffic, trick the system during setup, and then peek into supposedly protected virtual machines anyway. That’s the scary part. The even spicier part? The comments were basically a brawl between “this is devastating” and “this is old news, calm down.”
One camp went full doompost. A top reaction sneered that “confidential computing” is just a sales pitch to get people comfortable using someone else’s machine, while another commenter all but rolled their eyes at the idea there was ever a truly working concept here in the first place. The vibe was less “surprised” and more “I knew this magic trick was fake.” Another person raised the painfully practical question: if privacy is this shaky, maybe paying for an entire physical server is cheaper than dealing with a breach later.
But not everyone joined the panic parade. One reply pointed out that AMD already has microcode updates for this, while a skeptic hit the thread with the classic security-forum shrug: “Requires an already compromised hypervisor / UEFI. Yawn.” Translation: yes, it’s bad, but only if the landlord is already evil. Which, to be fair, is exactly the nightmare this tech claims it’s supposed to handle.
Key Points
- •Fabricked is a software-based attack that manipulates AMD Infinity Fabric memory routing to break AMD SEV-SNP protections.
- •The article says untrusted UEFI firmware is responsible for locking down parts of Infinity Fabric configuration during boot.
- •By skipping those lock-down calls, an attacker can keep Infinity Fabric configurable even after SEV-SNP is activated.
- •A malicious hypervisor can then interfere with PSP memory writes during SNP initialization and prevent proper RMP setup.
- •With the RMP left in insecure default states, SEV-SNP initialization appears successful but CVM memory protections are effectively bypassed.