FYI -- This bug reminds me of the old IBM 1403 chain printer hack: printing a not-so-random row of characters would cause all of the hammers to fire simultaneously, thus breaking the printer chain quite spectacularly. https://en.wikipedia.org/wiki/IBM_1403 BTW, it's only a matter of time before DRAM modules incorporate built-in caches/malware that can be triggered by a precise sequence of memory addresses and/or contents. It makes one seriously wonder about the safety and availability of computers, most of whose components come from offshore vendors with uncertain loyalties. The next war might well be fought using mechanical typewriters and slide rules. http://arxiv.org/abs/1507.06955 Rowhammer.js: A Remote Software-Induced Fault Attack in JavaScript As DRAM has been scaling to increase in density, the cells are less isolated from each other. Recent studies have found that repeated accesses to DRAM rows can cause random bit flips in an adjacent row, resulting in the so called Rowhammer bug. This bug has already been exploited to gain root privileges and to evade a sandbox, showing the severity of faulting single bits for security. However, these exploits are written in native code and use special instructions to flush data from the cache. In this paper we present Rowhammer.js, a JavaScript-based implementation of the Rowhammer attack.