Fabricked: Misconfiguring Infinity Fabric to Break AMD SEV-SNP
negura
44 points
21 comments
May 17, 2026
Related Discussions
Found 5 related stories in 1062.0ms across 14,015 title embeddings via pgvector HNSW
- The RCE that AMD wouldn't fix MrBruh · 250 pts · June 11, 2026 · 53% similar
- Copy Fail, Dirty Frag, and Fragnesia kernel vulnerabilities akhuettel · 120 pts · May 19, 2026 · 51% similar
- FatGid: FreeBSD 14.x kernel local privilege escalation WhyNotHugo · 92 pts · May 21, 2026 · 48% similar
- Users cry foul after AMD stripped memory crypto from its consumer CPUs helterskelter · 11 pts · June 15, 2026 · 48% similar
- Users cry foul after AMD stripped memory crypto from its consumer CPUs Cider9986 · 44 pts · June 16, 2026 · 48% similar
Discussion Highlights (5 comments)
nine_k
I wonder how much more expensive it is to rent the whole physical machine at all times for confidential computing purposes, compared to the losses incurred by a breach.
userbinator
More evidence that "confidential computing" is just a trick to convince people to hand over control of their computing to "someone else's machine". Never trusted the clown, and never will.
edelbitter
What purpose does the "news" of finding another way to break "confidential computing" serve, other than proliferate the incorrect assumption that there even was a working concept beforehand?
eggnet
There are microcode updates for this already https://www.amd.com/en/resources/product-security/bulletin/a...
procone
Requires an already compromised hypervisor / UEFI. Yawn.