GPUHammer: Rowhammer Attacks on GPU Memories are Practical
cs.CR
Submitted: 2025-07-10
Updated: 2026-09-16
Comments: 20 pages, including appendices. The paper was presented at SEC'25 (https://www.usenix.org/conference/usenixsecurity25)
Code: https://github.com/sith-lab/gpuhammer
License: http://creativecommons.org/licenses/by/4.0/
The gist: Rowhammer is a read disturbance vulnerability in modern DRAM that causes bit-flips, compromising security and reliability.
Terminology
Abstract
Rowhammer is a read disturbance vulnerability in modern DRAM that causes bit-flips, compromising security and reliability. While extensively studied on Intel and AMD CPUs with DDR and LPDDR memories, its impact on GPUs using GDDR memories, critical for emerging machine learning applications, remains unexplored. Rowhammer attacks on GPUs face unique challenges: (1) proprietary mapping of physical memory to GDDR banks and rows, (2) high memory latency and faster refresh rates that hinder effective hammering, and (3) proprietary mitigations in GDDR memories, difficult to reverse-engineer without FPGA-based test platforms. We introduce GPUHammer, the first Rowhammer attack on NVIDIA GPUs with GDDR6 DRAM. GPUHammer proposes novel techniques to reverse-engineer GDDR DRAM row mappings, and employs GPU-specific memory access optimizations to amplify hammering intensity and bypass mitigations. Thus, we demonstrate the first successful Rowhammer attack on a discrete GPU, injecting up to 8 bit-flips across 4 DRAM banks on an NVIDIA A6000 with GDDR6 memory. We also show how an attacker can use these to tamper with ML models, causing significant accuracy drops (up to 80%).
Sources
- Jailbreaking Black Box Large Language Models in Twenty Queries
- Explaining and Harnessing Adversarial Examples
- DenseNet: Implementing Efficient ConvNet Descriptor Pyramids
- Very Deep Convolutional Networks for Large-Scale Image Recognition
Related papers
- SoK: AI-Augmented Binary Reversing
- Relaxed Sender Anonymity for CBDC Interbank Settlement: A Zero-Knowledge Approach on Permissioned EVM
- Calibration-Family Overfit: Why Trusted Sabotage Monitors Don't Transfer Across Lineages
- Efficient Fuzzy PSI under One-Sided Assumptions
- Sealing the Audit-Runtime Gap for LLM Skills
- Token Composition: A Graph Based on EVM Logs