MIT researchers discover TONTOU, a Spectre variant bypassing Intel and AMD CPU defences

A gap measured in nanoseconds, but enough to slip back in
How TONTOU exploits the timing window between CPU state neutralization and branch predictor use.
Mark

Why does a gap measured in nanoseconds matter? That's billionths of a second.

Mimi

Because an attacker doesn't need much time if they know exactly what to do. They schedule an interrupt to land in that window, and in those nanoseconds, they can re-poison the processor's prediction machinery. It's like slipping back into a room you were just locked out of.

Mark

But you said the data extraction rate is only five bytes per second. That's incredibly slow.

Mimi

It is. But slowness doesn't make it impossible—it makes it impractical for casual attackers. For someone with time, resources, and access to a system, eighteen minutes to extract password hashes is not unreasonable.

Mark

Why did AMD patch this but Intel didn't?

Mimi

Intel's position is that the attack requires so many specific conditions that it's not worth the engineering effort to defend against. AMD disagreed. It's a judgment call about risk tolerance, and the two companies landed in different places.

Mark

Is this a problem for regular people?

Mimi

Not in the way a ransomware attack is. The real danger is in cloud environments where your code runs on the same hardware as someone else's. If you're running a laptop at home, you're not the target.

Mark

So Spectre is still not solved?

Mimi

Spectre revealed that the entire architecture of modern processors has a fundamental tension between speed and security. You can patch individual attacks, but you can't patch the underlying design. TONTOU is just another manifestation of that tension.

  • A nanosecond-wide gap in CPU defences — the 'post-neutralisation window' — gives attackers just enough room to re-poison branch prediction structures before sensitive operations complete.
  • MIT researchers demonstrated real, not theoretical, harm: on AMD Zen 2 systems they defeated kernel address randomization in all ten attempts and extracted password hash locations from live Linux machines.
  • The attack is technically demanding and slow — roughly five bytes per second, with a full exploit taking up to eighteen minutes — making it a negligible threat to ordinary users but a serious concern for cloud and multi-tenant environments.
  • AMD responded with a kernel patch after coordinated disclosure; Intel declined additional mitigations, citing the attack's complexity, though it acknowledged the research with a bug-bounty payment.
  • The divergent responses from the two chip giants signal that Spectre-class vulnerabilities are not a solved problem but an ongoing architectural reckoning with no clean resolution in sight.

Eight years after Spectre exposed a fundamental tension at the heart of modern computing, MIT researchers have found that the defenses built in response carry a flaw of their own — a nanosecond-wide gap between when a processor cleans up sensitive prediction data and when it actually uses it. Named TONTOU, the attack exploits this almost imperceptible window to re-poison the very machinery chip makers thought they had secured. The discovery is less a story of a single vulnerability than a reminder that the trade-off between speed and security, baked into processor design decades ago, continues to surface in forms no one fully anticipated.

Eight years after Spectre shook processor security to its core, MIT researchers Daniël Trujillo and Mengjia Yan have found another crack in the defences chip makers built in response. Their attack, called TONTOU — Time-of-Neutralization to Time-of-Use — exploits something almost impossibly small: the gap between the moment a processor clears sensitive prediction data and the moment it actually uses that data. In that sliver of time, measured in nanoseconds, an attacker can slip back in and re-poison the branch predictor's internal structures.

Branch prediction allows processors to guess upcoming instructions and execute them speculatively, accelerating performance. When guesses are wrong, results are discarded — but traces linger. Spectre has always exploited those traces. Since 2018, chip makers have tried to prevent attackers from tampering with prediction structures before sensitive operations. What Trujillo and Yan found is that the cleanup and the use are two separate events, and the space between them is exploitable. Using high-frequency timer interrupts, they injected re-poisoning precisely within that window on Intel Cascade Lake and Arrow Lake chips, and on AMD Zen 2 and Zen 4 architectures. Both families proved vulnerable.

The researchers built a working exploit to prove the point. On a standard AMD Zen 2 system running Linux, they defeated KASLR — the randomization that hides where sensitive kernel code lives in memory — in all ten attempts. In five of those runs, they extracted the location of the file storing privileged password hashes. This was real data leakage from a real system.

The attack is not an imminent threat to ordinary users. At roughly five bytes per second, a complete exploit could take eighteen minutes and demands precise timing and deep technical expertise. The risk is far higher in cloud and multi-tenant environments, where untrusted code runs alongside sensitive workloads.

AMD released a kernel patch following coordinated disclosure. Intel, citing the number of conditions required to mount the attack, declined additional mitigations — though it acknowledged the research with a bug-bounty payment. The gap in their responses reflects a deeper reality: Spectre was never a problem with a single fix. It was a revelation about the architecture of modern processors, and every defence built since has created new surfaces to probe. TONTOU is the latest evidence that the tension between speed and security remains very much unresolved.

Eight years after Spectre shook the foundations of processor security, researchers at MIT have found yet another crack in the defenses that chip makers built to patch the original wound. The new attack, called TONTOU, exploits something almost impossibly small: a gap measured in nanoseconds between the moment a processor neutralizes sensitive information and the moment it actually uses that information. In that sliver of time, an attacker can slip back in and poison the processor's prediction machinery all over again.

Daniël Trujillo and Mengjia Yan, working at MIT's Computer Science and Artificial Intelligence Laboratory, spent months studying how Intel and AMD processors handle branch prediction—the technique that lets chips guess which instructions are coming next and start executing them before they're certain. When a guess is wrong, the processor throws away the results, but traces linger in internal structures. Spectre exploits those traces. Since 2018, chip makers have tried to prevent attackers from tampering with branch prediction before sensitive operations. What Trujillo and Yan discovered is that the defense itself has a flaw: the act of cleaning up the prediction machinery and the act of using it are two separate events, separated by what they call a "post-neutralisation window."

TONTOU stands for Time-of-Neutralization to Time-of-Use. The researchers weaponized it using interrupt injection—a technique that schedules high-frequency timer interrupts to land precisely within that narrow window, allowing them to re-poison structures like the return stack buffer and branch history buffer. They tested the approach on Intel's Cascade Lake Refresh and Arrow Lake chips, and on AMD's Zen 2 and Zen 4 architectures. Both families proved vulnerable. On AMD systems, the window was sometimes only two instructions wide, lasting tens of nanoseconds. Yet they found a way through.

The real proof came when they built a working exploit. On an AMD Zen 2 system running standard Linux, they defeated KASLR—kernel address space layout randomization, a fundamental defense that randomizes where sensitive kernel code lives in memory. They succeeded in all ten attempts. In five of those runs, they extracted the location of /etc/shadow, the file containing password hashes for privileged accounts. This was not theoretical. This was real data leakage from a real system.

But TONTOU is not the kind of attack that will compromise your laptop tomorrow. The researchers measured a data extraction rate of around five bytes per second. A complete exploit could take eighteen minutes. The attack demands significant technical knowledge, precise timing, and a carefully controlled environment. For ordinary desktop users, the risk is negligible. For cloud providers and multi-tenant systems—where untrusted code runs alongside sensitive workloads—the calculus is different.

The researchers disclosed their findings to AMD in February and to Linux kernel maintainers in March. AMD released a kernel patch. Intel, by contrast, told the researchers it has no plans for additional mitigations, citing the number of conditions required to make the attack work. Intel did acknowledge the research with a bug-bounty payment. The divergence in response underscores a deeper truth: Spectre was never a problem with a single fix. It was a revelation about how modern processors work, and the defenses built since have been playing catch-up in a system that was never designed with this kind of threat in mind.

Years after the original disclosure, the underlying vulnerability remains. The challenge is not that processors are broken—they work brilliantly at what they were designed to do. The challenge is that speed and security were never meant to coexist, and every defense creates new surfaces to attack. TONTOU is just the latest proof that the tension between them has not been resolved.

Intel stated it does not intend to introduce additional mitigations for TONTOU, citing the number of conditions required for successful exploitation
— Intel
The attack requires significant technical knowledge, precise timing, and a suitable environment in which the necessary conditions can be established
— MIT researchers
Quer a matéria completa? Leia o original em Tech Edition ↗
Fale Conosco FAQ