LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a physical-access risk against encrypted Linux systems that auto-unlock disks from TPM during GRUB boot. If boot fails into GRUB rescue after filesystem corruption, the disk may already be decrypted, leaving data accessible without another authentication prompt.

Executive priority

Treat this as a targeted data-at-rest exposure issue. It is most urgent for mobile devices, remote sites, labs, and environments where attackers may gain physical access to encrypted systems.

Technical view

GRUB2 systems using LUKS with TPM-based auto-decryption can load the disk key into memory before validating the root filesystem. If the filesystem superblock is corrupted and GRUB enters rescue mode, the decrypted device and key may remain available, affecting confidentiality and integrity.

Likely exposure

Exposure is most likely on RHEL 7, 8, 9, 10, and OpenShift Container Platform 4 systems using RHCOS where LUKS disk encryption is paired with GRUB TPM auto-decryption. The attacker needs physical access and a way to alter the underlying filesystem.

Exploitation context

The bundle does not report active exploitation, and KEV is false. This is not a typical remote enterprise-wide vulnerability; the practical concern is stolen, seized, or physically accessible machines using unattended TPM-based disk unlock.

Researcher notes

The core condition is ordering: TPM auto-unlock occurs before GRUB fails into rescue after filesystem corruption. The source bundle names affected Red Hat platforms and includes an upstream GRUB rescue reader diff, but it does not provide complete remediation details.

Mitigation direction

  • Check Red Hat and GRUB guidance for available updates or vendor-approved workarounds.
  • Prioritize physical security for affected laptops, edge nodes, and remote infrastructure.
  • Review whether TPM auto-decryption is appropriate for high-risk systems.
  • Apply vendor-provided GRUB2 or RHCOS updates when available.
  • Use stronger boot-time authentication where operationally feasible.

Validation and detection

  • Inventory systems running affected RHEL or OpenShift/RHCOS versions.
  • Identify hosts using LUKS encryption with GRUB TPM auto-decryption.
  • Confirm whether boot rescue access is protected by vendor-supported controls.
  • Review asset theft, data-at-rest, and physical access risk for exposed systems.
  • Track Red Hat advisory status for package or platform remediation.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-4382 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N0.75.2redhat

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2025-4382Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineredhat

    Reported to Red Hat.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorgrub2grub2, 0unaffected
Red HatRed Hat Enterprise Linux 10grub2affected
Red HatRed Hat Enterprise Linux 7grub2affected
Red HatRed Hat Enterprise Linux 8grub2affected
Red HatRed Hat Enterprise Linux 9grub2affected
Red HatRed Hat OpenShift Container Platform 4rhcosaffected
Weakness

CWE details

CWE-306

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs