CVE-2025-4382: Grub2: grub allow access to encrypted device through cli once root device is unlocked via tpm

Published May 6, 2025
·
Updated

A flaw was found in systems utilizing LUKS-encrypted disks with GRUB configured for TPM-based auto-decryption. When GRUB is set to automatically decrypt disks using keys stored in the TPM, it reads the decryption key into system memory. If an attacker with physical access can corrupt the underlying filesystem superblock, GRUB will fail to locate a valid filesystem and enter rescue mode. At this point, the disk is already decrypted, and the decryption key remains loaded in system memory. This scenario may allow an attacker with physical access to access the unencrypted data without any further authentication, thereby compromising data confidentiality. Furthermore, the ability to force this state through filesystem corruption also presents a data integrity concern.

Other sources

When using encrypted LUKS devices as a disk being unlocked through a TPM device and grub fails to find a underlying filesytem, the boot manager will go into rescue mode and will still have the encryption key in memory. This allows an attacker with physical access to the target machine to access encrypted that through grub CLI which should not be accessible in this scenario.

Red Hat

Affected Software

1 affected component
GNU GRUB 2

Event History

May 6, 2025
Data Sourced
via Red Hat·02:34 PM
DescriptionSeverityAffected Software
May 9, 2025
CVE Published
via MITRE·11:59 AM
Data Sourced
via MITRE·11:59 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-4382?

CVE-2025-4382 is regarded as a high severity vulnerability due to the potential for physical access attacks.

2

How do I fix CVE-2025-4382?

To mitigate CVE-2025-4382, it is recommended to disable TPM-based auto-decryption and utilize alternative encryption management strategies.

3

Who is affected by CVE-2025-4382?

CVE-2025-4382 affects systems using LUKS-encrypted disks with GNU GRUB configured for TPM-based auto-decryption.

4

What type of attack can exploit CVE-2025-4382?

CVE-2025-4382 can be exploited through physical access to the system, allowing an attacker to manipulate memory to retrieve decryption keys.

5

What does CVE-2025-4382 involve regarding encryption management?

CVE-2025-4382 involves a flaw in how GRUB handles TPM-stored keys during the auto-decryption of LUKS-encrypted disks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203