Spaghettifying DRAM
Source Entity
Hacker News

Researchers have developed 'skitter-creek-bath-salts,' a technique that exploits DRAM controller translation registers in AMD Family 16h CPUs. This method bypasses memory protections to access sensitive areas like the PSP, SMM, and microcode by rewiring physical memory addresses.
Unveiling the Vulnerability: The 'skitter-creek-bath-salts' Exploit
The recent disclosure regarding the 'skitter-creek-bath-salts' technique highlights a critical vulnerability in legacy hardware architecture, specifically targeting AMD Family 16h CPUs. By manipulating the DRAM controller's translation registers, this exploit allows an attacker to bypass standard memory boundaries and access protected system areas. This research underscores the inherent risks associated with hardware-level memory management when documentation and security controls are insufficient.
Mechanics of Memory Rewiring
At its core, the exploit functions by 'poking' the DRAM controller to force memory addresses to map to arbitrary physical locations. By rewiring these translations, the technique dismantles the virtual walls that typically isolate the operating system kernel from sensitive platform components. This effectively grants access to the Platform Security Processor (PSP), System Management Mode (SMM), and microcode—areas that are usually completely invisible to the kernel and standard security software.
The Legacy Hardware Problem
The choice of AMD Family 16h CPUs as the primary target is significant, as these processors represent the final generation where the DRAM controller’s translation registers were explicitly documented in technical datasheets. Crucially, this documentation revealed that these specific registers could not be locked, leaving them permanently exposed to unauthorized modification. This highlights a recurring issue in hardware security: legacy components often contain immutable design flaws that are only fully understood after the hardware has reached end-of-life status.
Implications for Modern Security
While the exploit was tested on older architecture, it raises profound questions regarding the security of subsequent generations. Following the 16h series, AMD ceased documenting these specific translation registers in public datasheets. Whether this was an intentional security-through-obscurity measure or a failure to disclose remains a subject of concern. If newer CPUs retain similar underlying structures, they may harbor 'hidden' vulnerabilities that are simply waiting to be discovered by those willing to reverse-engineer the undocumented controllers.
Broader Systemic Risks
The ability to access specialized carveouts—memory regions reserved for critical firmware operations—effectively nullifies the security assumptions upon which modern computing relies. When the foundations of memory translation collapse, the entire stack of security features, from kernel-level protections to hardware-backed encryption, becomes suspect. This research proves that even if an operating system is secure, a compromised memory controller can render those protections moot.
Future Trends in Hardware Hardening
This disclosure serves as a stark reminder of the necessity for rigorous hardware transparency. As security researchers continue to probe the lowest levels of the silicon, manufacturers will face increasing pressure to provide clear, actionable documentation and implement robust locking mechanisms for memory controllers. Moving forward, the industry must prioritize 'security by design' to ensure that memory translation layers are not just functional, but inherently resistant to the type of manipulation demonstrated by the skitter-creek-bath-salts project.