<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cybercrime.club</title><link>https://cybercrime.club/tags/hardware-security/</link><description>Infrastructure security news for people who build infrastructure.</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 14:05:42 -0400</lastBuildDate><atom:link href="https://cybercrime.club/tags/hardware-security/" rel="self" type="application/rss+xml"/><item><title>The ECC Excuse Is Dead: A Hardening Guide for Multi-Tenant GPU Infrastructure After GPUThor</title><link>https://cybercrime.club/deep-dives/ecc-dead-multi-tenant-gpu-hardening-rowhammer/</link><pubDate>Sun, 30 Aug 2026 14:05:42 -0400</pubDate><guid>https://cybercrime.club/deep-dives/ecc-dead-multi-tenant-gpu-hardening-rowhammer/</guid><description>For four months, 'enable ECC' was the official fix for GPU Rowhammer. GPUThor just showed that advice was wrong. Here's what to actually change on GPU fleets that run untrusted CUDA code from more than one tenant.</description></item></channel></rss>