September 15, 2025
Rowhammer remains one of the most stubborn and persistent physical hardware vulnerabilities in modern Dynamic Random-Access Memory (DRAM). By repeatedly activating ("hammering") specific memory rows, electrical charge leaks across silicon boundaries, inducing unintended bit flips in adjacent memory cells without requiring any software exploits.
Why Securing the DRAM Ecosystem Matters
- Persistent Threat to Isolation: Rowhammer bit flips can be weaponized by local processes or multi-tenant cloud workloads to corrupt page tables, achieve kernel privilege escalation, and break cryptographic signatures and sandbox boundaries.
- Limitations of Existing Defenses: Memory manufacturers introduced hardware mitigations including Target Row Refresh (TRR) in DDR4 and on-die Error Correction Code (ECC) in DDR5. However, sophisticated multi-sided and synchronized hammering access patterns (such as Half-Double, Blacksmith, and Phoenix) have repeatedly proven that proprietary on-die mitigations can be circumvented.
- Google's Research Initiatives: To address these systemic hardware vulnerabilities, Google actively supports academic research partnerships and the development of open security fuzzing and stress-testing platforms for DDR5 memory modules.
- The Path to Resilient Memory: Mitigating Rowhammer long-term requires industry-wide transparency, standardized validation benchmarks, and memory controller architectures capable of guaranteed, deterministic row refresh without unbearable performance and energy overheads.
📖 Read the complete article on the Google Security Blog:
Supporting Rowhammer research to protect the DRAM ecosystem