Thunderbolt Is PCIe, Extended Out Through a Port
Most external ports, a standard USB-A jack, for example, connect a peripheral to the system through a controller that mediates what the device can access. Thunderbolt works differently. It tunnels PCI Express, the same high-speed internal bus that graphics cards and NVMe drives use, out through an external connector. That's what makes Thunderbolt fast enough to drive an external GPU or a multi-monitor dock over a single cable. It's also what makes it a much more privileged interface than USB: a PCIe device isn't just handing data to the operating system through a driver, it can be granted direct memory access, DMA, which means reading and writing system RAM without going through the CPU or the OS at all.
Direct memory access exists because it's useful. It's how a graphics card moves frame data efficiently, and how a fast storage controller avoids CPU overhead on every read and write. The security problem is that a malicious PCIe device, connected through a Thunderbolt port, can ask for the same kind of access and use it to read encryption keys, session tokens, or anything else sitting in memory while the machine is running, whether or not the screen is locked.
What Thunderspy Actually Demonstrated
In 2020, researcher Bjorn Ruytenberg at Eindhoven University of Technology published Thunderspy, a set of attacks against Thunderbolt's security model. The research showed that with a few minutes of physical access to a Thunderbolt port, an attacker could reprogram the controller's firmware to clone the identity of an already-trusted device, or in some cases disable Thunderbolt security checks entirely, even on systems where the more restrictive security levels were enabled and even when the machine was locked or in sleep. Some of the described attacks required opening the laptop case briefly to attach hardware directly to the Thunderbolt controller; others worked through the port alone.
The finding wasn't that Thunderbolt has a bug. It's that the security model assumed a level of attacker effort that turned out to be lower than expected, and that firmware-level trust decisions made once at pairing time weren't being re-verified strongly enough afterward.
This class of attack sits in the same family as cold boot attacks in that both target data sitting in memory rather than data at rest, but the mechanism is different. Cold boot attacks exploit the physical property that RAM contents fade rather than vanish instantly after power loss. DMA attacks over Thunderbolt exploit a live, powered, running system through a legitimate hardware interface designed to grant broad access.
The Mitigations That Followed
Intel's response was Kernel DMA Protection, which uses the system's IOMMU (the same VT-d or AMD-Vi hardware used for virtualization memory isolation) to restrict what a Thunderbolt-connected PCIe device can access before the operating system has explicitly authorized it. On supporting hardware and operating systems, this closes most of the pre-boot and pre-authorization window that Thunderspy relied on. The protection isn't universal retroactively: it depends on firmware and OS support that older systems, including many machines from before Kernel DMA Protection existed, simply don't have.
Thunderbolt 4 made this stronger by requiring Kernel DMA Protection as part of the certification specification itself, rather than leaving it as an optional implementation detail the way Thunderbolt 3 did. That's a meaningful difference: a Thunderbolt 3 machine's actual exposure depends on whether its specific vendor implemented the protection, while a certified Thunderbolt 4 machine is required to have it.
Apple's implementation on Mac hardware has followed a somewhat different path, layered on top of the T2 security chip on Intel-based Macs and, since the shift to Apple Silicon, on the tighter hardware and firmware integration of the M-series systems. The practical effect has been a narrower attack surface than a typical Windows laptop of the same era, though "narrower" isn't the same as "immune," and researchers have continued to probe Thunderbolt and USB4 implementations across vendors as the specification itself evolves. The lesson generalizes past any one platform: DMA protection is a property of the specific firmware and OS combination running on a given machine, not a property of the word "Thunderbolt" printed next to the port.
| Configuration | DMA exposure |
|---|---|
| Thunderbolt 3, Kernel DMA Protection not implemented | Full pre-Thunderspy-mitigation exposure while unlocked or briefly accessible |
| Thunderbolt 3, Kernel DMA Protection implemented | Significantly reduced, but depends on OS and firmware support |
| Thunderbolt 4 (certification requires the protection) | Kernel DMA Protection mandatory by specification |
| Thunderbolt disabled entirely in firmware | No PCIe tunneling exposure through the port at all |
Sleep, Not Just Lock, Is the Exposure Window That Matters
A locked screen with the system still fully powered and running is meaningfully different from a system that's been shut down or hibernated with the disk fully unmounted. Full-disk encryption protects data at rest, when the machine is off, but a locked or sleeping machine still has decryption keys and unlocked data sitting in RAM, which is exactly what a DMA attack targets. This is the same underlying exposure that evil maid attacks exploit more broadly, brief unsupervised physical access to a device that's locked but still running, though DMA over Thunderbolt is a specific technical path into that broader category rather than a synonym for it.
What Actually Reduces the Risk
For most people, the practical exposure is low: this requires physical access and specialized hardware, not something a remote attacker can do. It matters most for anyone who leaves a laptop briefly unattended in a context where a skilled adversary might have physical access, a hotel room, a border crossing, a shared workspace. Where it matters, the concrete steps are disabling Thunderbolt entirely in firmware settings when it's not in active use, keeping firmware and OS updated so Kernel DMA Protection stays current, and fully shutting down rather than sleeping when leaving a device unattended for any length of time, since a powered-off machine with secure boot and full-disk encryption removes the live-memory attack surface entirely.
None of this argues against Thunderbolt as a technology. The speed it enables is real and useful. It argues for treating an external port that can request direct memory access the way you'd treat any other high-privilege interface: something to be deliberate about, not something to assume is safe by default because it looks like an ordinary cable.