/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Google researchers detail “Half-Double”, a new Rowhammer attack technique they say will be difficult to mitigate as future generations of DRAM chips get smaller

A full fix for the “Half-Double” technique will require rethinking how memory semiconductors are designed. Tweets: @ucsdjacobs , @gadgetlab , and @wired Tweets: UCSD Engineering / @ucsdjacobs : As chips shrink, #rowhammer attacks get harder to stop: @ucsd_cse postdoc Daniel Moghimi is quoted in this @WIRED story by @lilyhnewman: https://www.wired.com/... #cybersecurity @gadgetlab : A full fix for the “Half-Double” technique will require rethinking how memory semiconductors are designed. https://www.wired.com/... @wired : Google findings carry an additional warning that advances in the size and efficiency of memory chips potentially come with new risks from Rowhammer. https://www.wired.com/...

Wired Lily Hay Newman

Context & Ripple Effects

Half-Double is the latest step in a five-year escalation Google and academic researchers have tracked against DRAM itself. The arc already ran through attacks on ECC memory once thought impervious, which widened the target set to servers and routers, and through RAMBleed, which turned bit-flipping into actual data theft despite error correction.

First-order effects

  • Google's disclosure hands DRAM designers a defect rooted in shrinking cell geometry — the fix Wired reports is required is a redesign of how memory semiconductors are laid out, not a patch.
  • The same team had already argued, via its Spectre-like attack with no known mitigation, that software defenses carry too high a performance cost — so buyers can't expect an OS-level answer here either.

Second-order effects

  • Each disclosed variant erodes the assumptions server and router operators rely on: ECC was sold as the boundary, then RAMBleed and the ECC-targeting work dissolved it, and the follow-on exploit later defeated recent hardware mitigations on all 40 PC-DDR4 devices tested (full DDR4 defeat).
  • Memory vendors face a compounding tax on density roadmaps: every process shrink now has to be re-validated against Rowhammer-style leakage, adding design cost precisely where margins depend on scaling.

Third-order effects

  • If mitigation keeps lagging disclosure, security certification shifts upstream into silicon design — memory becomes a component whose trustworthiness is audited at fabrication time rather than patched in the field.
  • The broader pattern across Spectre-class and Rowhammer-class research is that performance-driven microarchitectural shortcuts are becoming a standing attack surface, forcing the industry to price security into every future generation of chips.

The trend: Hardware side-channel research is outrunning field-patchable defenses, pushing security responsibility from OS vendors toward chip designers as DRAM geometries shrink.