For two years, a Linux change left disk-encryption keys sitting in RAM through suspend (mathstodon.xyz)
The mechanism at issue is cryptsetup's luksSuspend, which is supposed to scrub the master key from memory before sleep. The claim: it quietly stopped, leaving the key resident and, in the post's words, 'for the taking by anyone who seized the still-powered laptop.'
The thread's corrections matter as much as the bug. Several readers noted luksSuspend is a Debian extension, so the headline overstates a kernel-wide flaw. Others questioned the threat model — a locked laptop isn't trivially readable by 'anyone' — and the most practical fix offered was to hibernate: power the RAM off and the whole class of cold-boot attack goes away.
Sign in to save