CVE-2025-4382

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.

CVSS v3 5.9 MEDIUM

5.9^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 0.7 / Impact : 5.2

Attack Vector PHYSICAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

References

Link	Resource
https://access.redhat.com/security/cve/CVE-2025-4382
https://bugzilla.redhat.com/show_bug.cgi?id=2364416

Configurations

No configuration.

History

12 May 2025, 17:32

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-05-09 12:15

Updated : 2025-05-12 17:32

NVD link : CVE-2025-4382

Mitre link : CVE-2025-4382

CVE.ORG link : CVE-2025-4382

JSON object : View

Products Affected

No product.

CWE

CWE-306

Missing Authentication for Critical Function

{"id": "CVE-2025-4382", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "PHYSICAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 0.7}]}, "published": "2025-05-09T12:15:33.657", "references": [{"url": "https://access.redhat.com/security/cve/CVE-2025-4382", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2364416", "source": "secalert@redhat.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-306"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Se detect\u00f3 una falla en sistemas que utilizan discos cifrados con LUKS con GRUB configurado para el descifrado autom\u00e1tico basado en TPM. Cuando GRUB est\u00e1 configurado para descifrar autom\u00e1ticamente los discos mediante claves almacenadas en el TPM, lee la clave de descifrado en la memoria del sistema. Si un atacante con acceso f\u00edsico logra corromper el superbloque del sistema de archivos subyacente, GRUB no podr\u00e1 localizar un sistema de archivos v\u00e1lido y entrar\u00e1 en modo de rescate. En este punto, el disco ya est\u00e1 descifrado y la clave de descifrado permanece cargada en la memoria del sistema. Esta situaci\u00f3n podr\u00eda permitir que un atacante con acceso f\u00edsico acceda a los datos sin cifrar sin necesidad de autenticaci\u00f3n adicional, comprometiendo as\u00ed la confidencialidad de los datos. Adem\u00e1s, la posibilidad de forzar este estado mediante la corrupci\u00f3n del sistema de archivos tambi\u00e9n plantea un problema de integridad de los datos."}], "lastModified": "2025-05-12T17:32:32.760", "sourceIdentifier": "secalert@redhat.com"}