BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-4382High confidence

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

Unknown · Unknown

5.9MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 77 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 1 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.35% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 77 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegrub2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcegrub2Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcegrub2Vendor fix publishedDebian records a fixed source-package version for this release.2.14~git20250718.0e36779-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcegrub2Vendor fix publishedDebian records a fixed source-package version for this release.2.14~git20250718.0e36779-2Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegrub2-signedUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegrub2-unsignedUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-4382 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygrub2: grub allow access to encrypted device through CLI once root device is unlocked via TPM
75 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • grub2-common as a component of Red Hat Enterprise Linux 10
  • grub2-efi-aa64 as a component of Red Hat Enterprise Linux 10
  • grub2-efi-aa64-cdboot as a component of Red Hat Enterprise Linux 10
  • grub2-efi-aa64-modules as a component of Red Hat Enterprise Linux 10
  • grub2-efi-x64 as a component of Red Hat Enterprise Linux 10
  • grub2-efi-x64-cdboot as a component of Red Hat Enterprise Linux 10
  • grub2-efi-x64-modules as a component of Red Hat Enterprise Linux 10
  • grub2-pc as a component of Red Hat Enterprise Linux 10
  • grub2-pc-modules as a component of Red Hat Enterprise Linux 10
  • grub2-ppc64le as a component of Red Hat Enterprise Linux 10
  • grub2-ppc64le-modules as a component of Red Hat Enterprise Linux 10
  • grub2-tools as a component of Red Hat Enterprise Linux 10
Summary
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.
Remediation
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-14163

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.9 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 77 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

A security-sensitive function is reachable without the authentication check that should protect it.

How

An attacker operating through physical access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

A security-sensitive function is reachable without the authentication check that should protect it.

How

An attacker operating through physical access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
physical access → Missing Authentication for Critical Function → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Physical
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-306 ↗

CWE-306: Missing Authentication for Critical Function. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVPhysicalAttack vector: The attacker needs physical access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
CWE-306
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-14163Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0995Grub: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann eine Schwachstelle in Grub ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4575 https://www.cve.org/CVERecord?id=CVE-2025-4575 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-46727 https://www.cve.org/CVERecord?id=CVE-2025-46727 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-2025-47153 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
04

Evidence and provenance

Published 9 May 2025 · Last source change 1 Sept 2026, 11:51 UTC · CWE-306 · Missing Authentication for Critical Function

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-14163
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    grub2-common as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64 as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64-cdboot as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64-modules as a component of Red Hat Enterprise Linux 10; grub2-efi-x64 as a component of Red Hat Enterprise Linux 10; grub2-efi-x64-cdboot as a component of Red Hat Enterprise Linux 10; grub2-efi-x64-modules as a component of Red Hat Enterprise Linux 10; grub2-pc as a component of Red Hat Enterprise Linux 10; grub2-pc-modules as a component of Red Hat Enterprise Linux 10; grub2-ppc64le as a component of Red Hat Enterprise Linux 10; grub2-ppc64le-modules as a component of Red Hat Enterprise Linux 10; grub2-tools as a component of Red Hat Enterprise Linux 10; grub2-tools-efi as a component of Red Hat Enterprise Linux 10; grub2-tools-extra as a component of Red Hat Enterprise Linux 10; grub2-tools-minimal as a component of Red Hat Enterprise Linux 10; grub2.src as a component of Red Hat Enterprise Linux 10; grub2 as a component of Red Hat Enterprise Linux 7; grub2-common as a component of Red Hat Enterprise Linux 7; grub2-efi as a component of Red Hat Enterprise Linux 7; grub2-efi-aa64-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32 as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32-cdboot as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-x64 as a component of Red Hat Enterprise Linux 7; grub2-efi-x64-cdboot as a component of Red Hat Enterprise Linux 7; grub2-efi-x64-modules as a component of Red Hat Enterprise Linux 7; grub2-pc as a component of Red Hat Enterprise Linux 7; grub2-pc-modules as a component of Red Hat Enterprise Linux 7; grub2-ppc-modules as a component of Red Hat Enterprise Linux 7; and 44 more
    After
    grub2-common as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64 as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64-cdboot as a component of Red Hat Enterprise Linux 10; grub2-efi-aa64-modules as a component of Red Hat Enterprise Linux 10; grub2-efi-x64 as a component of Red Hat Enterprise Linux 10; grub2-efi-x64-cdboot as a component of Red Hat Enterprise Linux 10; grub2-efi-x64-modules as a component of Red Hat Enterprise Linux 10; grub2-pc as a component of Red Hat Enterprise Linux 10; grub2-pc-modules as a component of Red Hat Enterprise Linux 10; grub2-ppc64le as a component of Red Hat Enterprise Linux 10; grub2-ppc64le-modules as a component of Red Hat Enterprise Linux 10; grub2-tools as a component of Red Hat Enterprise Linux 10; grub2-tools-efi as a component of Red Hat Enterprise Linux 10; grub2-tools-extra as a component of Red Hat Enterprise Linux 10; grub2-tools-minimal as a component of Red Hat Enterprise Linux 10; grub2.src as a component of Red Hat Enterprise Linux 10; grub2 as a component of Red Hat Enterprise Linux 7; grub2-common as a component of Red Hat Enterprise Linux 7; grub2-efi as a component of Red Hat Enterprise Linux 7; grub2-efi-aa64-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32 as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32-cdboot as a component of Red Hat Enterprise Linux 7; grub2-efi-ia32-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-modules as a component of Red Hat Enterprise Linux 7; grub2-efi-x64 as a component of Red Hat Enterprise Linux 7; grub2-efi-x64-cdboot as a component of Red Hat Enterprise Linux 7; grub2-efi-x64-modules as a component of Red Hat Enterprise Linux 7; grub2-pc as a component of Red Hat Enterprise Linux 7; grub2-pc-modules as a component of Red Hat Enterprise Linux 7; grub2-ppc-modules as a component of Red Hat Enterprise Linux 7; and 45 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2025-14163↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-4382 · cve.blacktree.nl