Fabricked: Misconfiguring Infinity Fabric to Break AMD SEV-SNP
negura
44 points
21 comments
May 17, 2026
Related Discussions
Found 5 related stories in 80.1ms across 8,303 title embeddings via pgvector HNSW
- 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
- Fast16: High-precision software sabotage 5 years before Stuxnet dd23 · 205 pts · April 26, 2026 · 47% similar
- HDD Firmware Hacking jsploit · 167 pts · May 14, 2026 · 45% similar
- Guy builds AI driven hardware hacker arm from duct tape, old cam and CNC machine scaredpelican · 144 pts · April 16, 2026 · 45% 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.