Cybersecurity glossary
What is a Rowhammer Attack?
Learn what a Rowhammer attack is, how repeatedly accessing DRAM rows can flip bits in nearby memory, what security impacts researchers demonstrated, and which mitigations reduce risk.
Definition
A Rowhammer attack is a hardware-oriented exploit technique that repeatedly accesses (hammers) rows in DRAM to induce electrical disturbance bit flips in adjacent rows, potentially corrupting data or undermining memory isolation used by security boundaries.
Why Rowhammer matters
Security models often assume memory contents change only when software writes them. Rowhammer challenges that assumption: repeatedly reading one DRAM region can disturb neighboring cells enough to flip bits—zeros becoming ones or vice versa—without a direct write to the victim location.
Researchers showed these flips can corrupt page tables, cryptographic material, or isolation metadata in carefully arranged scenarios. For most organizations, Rowhammer is not the first operational fire to fight—but it is an important reminder that hardware reliability and security are linked.
How Rowhammer works
Identify hammerable memory
Attacker-controlled code or patterns repeatedly access specific DRAM rows.
Hammer adjacent rows
High-frequency activation creates electrical disturbance in nearby rows.
Induce bit flips
Victim cells change state unexpectedly under stress.
Align flips to security structures
Advanced exploits arrange memory so flips hit useful targets like page table entries.
Escalate or corrupt
Bit flips may enable privilege gains or break integrity of sensitive data.
Mitigate in hardware/firmware
TRR, improved refresh, firmware updates, and platform defenses reduce success.
Security impact classes
Integrity failures
Silent data corruption in applications that assume DRAM is reliable.
Isolation breaks
Research exploits targeting page tables or sandboxes via controlled flips.
Crypto degradation
Bit flips in keys or intermediate values can weaken cryptographic operations.
Cloud tenancy concerns
Shared hardware raises questions about cross-tenant disturbance in theory and research.
Mitigations and limits
| Control | Role |
|---|---|
| Target Row Refresh / improved refresh | Hardware attempts to refresh victims of hammering |
| Firmware / BIOS updates | Deliver platform-specific Rowhammer mitigations |
| ECC | Detect/correct some errors; incomplete alone |
| Least privilege / sandboxing | Makes obtaining a hammering foothold harder |
| Vendor guidance | Follow CPU/DRAM/cloud provider recommendations |
- Keep server and workstation firmware current as part of patch management.
- Prefer platforms with documented Rowhammer mitigations for multi-tenant workloads.
- Do not assume ECC equals immunity; treat it as one layer.
- Reduce local code execution opportunities that could run hammering patterns.
- Track vendor advisories for DRAM and memory-controller issues.
- For high-assurance systems, include hardware fault classes in threat models.
- Separate research hype from practical exploitability on your specific fleet.
- Combine hardware hygiene with strong software isolation controls.
The practical takeaway
A Rowhammer attack hammers DRAM rows until nearby bits flip, challenging software assumptions about memory integrity and isolation. It is a hardware disturbance effect that software can sometimes trigger.
Defend with modern platform mitigations, firmware updates, ECC where appropriate, and strong containment of local code execution. Treat memory as a physical system—not only a logical array of bytes.
Related security terms
Memory Corruption
Software memory safety bugs; Rowhammer instead induces physical bit flips in DRAM.
Privilege Escalation
A demonstrated impact class for some Rowhammer research exploits.
Side-Channel Attack
Another class of attacks that abuse physical/microarchitectural effects.
Remote Code Execution (RCE)
In extreme research cases, bit flips have been chained toward powerful outcomes.
Frequently asked questions
What is Rowhammer in simple terms?
Rowhammer is a way to stress computer memory so hard that tiny electrical effects flip bits in nearby memory cells. Those flipped bits can corrupt data or break security assumptions.
Is Rowhammer a software bug?
No. It is rooted in DRAM physics. Software can trigger the hammering pattern, but the bit flips are a hardware disturbance effect.
Can Rowhammer be exploited remotely?
Classic demos often need local code execution. Researchers have explored more constrained and remote-ish scenarios, but practical risk depends heavily on platform, mitigations, and attacker capabilities.
What is Target Row Refresh (TRR)?
TRR is a class of DRAM/controller mitigations that attempt to refresh neighboring rows when hammering is detected, reducing bit-flip likelihood.
Does ECC memory stop Rowhammer?
ECC can detect/correct some bit errors and raises attacker cost, but research has shown ECC is not a complete Rowhammer cure by itself.
Who should care most?
Cloud providers, browser vendors, OS vendors, and hardware manufacturers—anyone responsible for strong memory isolation between mutually distrusting tenants or processes.
What can defenders do today?
Keep firmware/microcode/BIOS updated, prefer hardware with modern mitigations, apply vendor guidance, and maintain least privilege so local footholds are harder to obtain.
References
Explore authoritative guidance and frameworks related to rowhammer attack.
Explore every security definition
Return to the glossary to search by term, alias, starting letter, or security category.