For decades, computers have followed a simple division of labor: memory stores data and processors compute on it. The problem? Constantly shuttling data back and forth between the two is slow and burns enormous amounts of energy — sometimes more than the computation itself. This bottleneck has a name: the "memory wall."

One promising end-run around this wall is called Processing-using-DRAM (PuD). The clever idea: DRAM chips are already massive grids of cells arranged in rows and columns. If you activate multiple rows simultaneously, the electrical interactions between them naturally produce logical operations (AND, OR, NOT) on the bits stored in those rows. In other words, your memory becomes a giant, free computer — no data movement required.

This paper asks an uncomfortable question: does PuD actually work reliably on real, modern DRAM chips? The authors took commercial DRAM and ran extensive experiments. Their finding, which they call PuDGhost, is troubling:

• As DRAM gets denser (cells packed closer together to increase capacity), neighboring cells start interfering with each other electrically.
• When you perform a PuD operation on one set of rows, that activity can silently corrupt unrelated data stored in nearby rows — rows that weren't part of the computation at all.
• This is essentially a computational version of the famous Rowhammer attack, but instead of malicious activity flipping bits, it's the chip's own intended computation that produces corruption as a side effect.

The implications are significant. PuD has been pitched as a transformative architecture for AI workloads, databases, and any application that grinds through large amounts of memory. But if running PuD operations can corrupt the very data they're supposed to operate on — or worse, data belonging to other processes — then the whole paradigm needs guardrails before it can ship in real systems.

The authors don't just diagnose the problem; they sketch implications for future systems: error-correction schemes, data-placement policies that keep "computational" rows away from sensitive ones, and refresh strategies that account for the disturbance PuD introduces. The takeaway is that researchers can't just simulate PuD on idealized models — the physics of real chips is messier than the theory assumes.