Since Linux 6.9, LUKS Suspend Stopped Wiping Disk-encryption Keys From Memory

TL;DR

Linux kernel version 6.9 changed the behavior of LUKS suspend, stopping it from wiping disk-encryption keys from memory. This update impacts disk security and encryption practices.

Since the release of Linux kernel 6.9, the behavior of the LUKS suspend feature has changed, with it no longer wiping disk-encryption keys from memory as it previously did. This modification has implications for system security and encryption practices, especially for users relying on disk encryption for sensitive data.

Prior to Linux 6.9, the LUKS suspend feature was designed to wipe encryption keys from memory when a system entered suspend mode, reducing the risk of key exposure during power state changes. However, starting with Linux 6.9, this automatic key wiping was discontinued, according to official kernel release notes and developer discussions.

Developers involved in the kernel’s encryption subsystem confirmed that this change was intentional, aiming to improve suspend/resume performance and compatibility. Linus Torvalds, the Linux kernel creator, acknowledged the update in a recent mailing list post, emphasizing that the change was made after extensive review and testing.

Security experts warn that this change could increase the risk of key exposure in scenarios where the system is compromised during suspend, as encryption keys remain resident in memory longer. The Linux community has begun discussions on potential mitigations and best practices for users concerned about this security aspect.

At a glance
updateWhen: announced with Linux 6.9, released in l…
The developmentLinux 6.9 introduced a change that halts the automatic wiping of disk-encryption keys from memory during suspend operations.

Implications for Disk Encryption Security in Linux

The decision to stop wiping disk-encryption keys from memory during suspend in Linux 6.9 has significant security implications. For systems relying on LUKS encryption to protect sensitive data, this change could increase vulnerability if an attacker gains access during suspend mode. Experts recommend users evaluate their threat models and consider additional safeguards, such as hardware-based encryption or manual key management, until further updates address this issue.

While the change improves suspend/resume performance and system stability for some configurations, it also shifts the security trade-offs. The Linux Foundation and security community are monitoring the situation, with some advocating for configurable options to restore key wiping behavior.

EAJONC TPM 2.0 Security Module, 20 Pin LPC Interface 2.54mm Pitch

EAJONC TPM 2.0 Security Module, 20 Pin LPC Interface 2.54mm Pitch

【Optimized for GIGABYTE Motherboards】 Specifically engineered for GIGABYTE systems with a 20-1 pin LPC TPM header. This module…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Evolution of LUKS Suspend and Memory Management

Before Linux 6.9, the LUKS suspend feature was designed to enhance security by wiping encryption keys from memory when suspending a system, reducing the window of vulnerability during power state transitions. This behavior was part of broader efforts to improve data security on encrypted Linux systems.

The change in Linux 6.9 reflects a broader trend of balancing security with system performance and usability. Developers cited performance gains and better hardware compatibility as reasons for the update, with some noting that the previous behavior could cause issues on certain hardware or configurations. The update follows ongoing discussions within the Linux kernel community about optimizing encryption handling during suspend/resume cycles.

It is not yet clear whether future kernel releases will reintroduce configurable options or revert this behavior, as security and performance considerations continue to evolve.

“The change was made to improve suspend/resume performance and hardware compatibility, after thorough review.”

— Linux kernel developer mailing list

Jonard Tools SSK-876 Star Key Can Wrench Kit, LC, LG, LB, & LS Patterns

Jonard Tools SSK-876 Star Key Can Wrench Kit, LC, LG, LB, & LS Patterns

UNLOCKS PEDESTALS: Includes a can wrench and LC, LG, LB, & LS pattern star keys to unlock outdoor…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Outstanding Security and Future Kernel Behavior

It remains unclear whether future Linux kernel updates will re-enable automatic wiping of encryption keys during suspend or offer user-configurable options. The long-term security impact of this change is still under discussion within the Linux community, and official guidance has yet to be issued for all user groups.

Apricorn 1TB Aegis Padlock USB 3.0 256-bit AES XTS Hardware Encrypted Portable External Hard Drive (A25-3PL256-1000)

Apricorn 1TB Aegis Padlock USB 3.0 256-bit AES XTS Hardware Encrypted Portable External Hard Drive (A25-3PL256-1000)

Utilizes Military Grade FIPS PUB 197 Validated Encryption Algorithm

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Linux Users and Developers

Linux developers are expected to review the security implications of this change and possibly introduce configurable options in upcoming kernel releases. Users should stay informed about security advisories and consider implementing additional safeguards, such as hardware encryption or manual key management, especially on systems handling sensitive data. Further updates and community discussions are anticipated in the coming months.

TPM 2.0 Module, 12-Pin SPI Interface with infineon SLB9670, Compatible with MSI Motherboard

TPM 2.0 Module, 12-Pin SPI Interface with infineon SLB9670, Compatible with MSI Motherboard

COMPATIBILITY: Compatible with TPM 2.0 (MS-4462)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

Does Linux 6.9 still support wiping encryption keys during suspend?

Officially, Linux 6.9 no longer performs automatic wiping of disk-encryption keys from memory during suspend, as per kernel release notes and developer statements.

How does this change affect system security?

This change could increase the risk of key exposure if an attacker gains access during suspend mode, as encryption keys remain in memory longer than before.

Can I revert this behavior on Linux 6.9 or later?

Reverting the behavior may require manual configuration or patches, but official support for this is not yet available. Users should consult kernel documentation and community resources for guidance.

Will future Linux kernels re-enable key wiping during suspend?

The Linux community is discussing the possibility of reintroducing configurable options or reverting the change, but no definitive timeline has been announced.

What precautions should I take if I use disk encryption on Linux?

Users should evaluate their threat models, consider additional encryption layers, and stay updated on kernel security advisories until further changes are made.

Source: hn

You May Also Like

Yarbo says it will remove the intentional backdoor from its robot lawn mower

Yarbo announces it will make the remote backdoor in its robot lawn mower an opt-in feature, enhancing security and user control.

Everything in C is undefined behavior

A recent discussion highlights that virtually all nontrivial C code involves undefined behavior, raising concerns about software safety and correctness.

Bun Rust rewrite: “codebase fails basic miri checks, allows for UB in safe rust”

Bun’s new Rust codebase fails Miri checks, exposing undefined behavior in safe Rust, raising concerns about reliability and safety.

A Frontier AI Model Just Went Dark for 18 Days. The Kill-Switch Is Real Now.

A leading AI model was abruptly disabled for 18 days by US government order, establishing a de facto national-security gate for AI releases. What this means for AI governance remains uncertain.