LiveActive security incident?Get immediate response
CVE Record

CVE-2025-0677: Grub2: ufs: integer overflow may lead to heap based out-of-bounds write when handling symlinks

A flaw was found in grub2. When performing a symlink lookup, the grub's UFS module checks the inode's data size to allocate the internal buffer to read the file content, however, it fails to check if the symlink data size has overflown. When this occurs, grub_malloc() may be called with a smaller value than needed. When further reading the data from the disk into the buffer, the grub_ufs_lookup_symlink() function will write past the end of the allocated size. An attack can leverage this by crafting a malicious filesystem, and as a result, it will corrupt data stored in the heap, allowing for arbitrary code execution used to by-pass secure boot mechanisms.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2025-0677 is a GRUB2 bootloader flaw in UFS symlink handling. A highly privileged local attacker could use a crafted filesystem to corrupt GRUB memory before the operating system starts, potentially bypassing Secure Boot. This is not described as remotely exploitable, but boot-chain compromise can have high business impact.

Executive priority

Treat this as a boot-chain hardening priority for affected Red Hat estates, especially sensitive servers, virtualization hosts, and OpenShift nodes. It does not show confirmed active exploitation in the provided evidence, so urgency should be risk-based rather than emergency-driven.

Technical view

GRUB2’s UFS module may fail to detect integer overflow in symlink size handling. The resulting undersized allocation can lead to a heap-based out-of-bounds write in grub_ufs_lookup_symlink() when reading crafted filesystem data. The CVSS vector is local, high complexity, high privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to Red Hat environments using affected GRUB2 or RHCOS builds. The bundle lists RHEL 9, RHEL 10, and OpenShift Container Platform 4 as affected, with RHEL 7 and 8 status unknown. Systems without UFS processing in the boot path may have reduced practical exposure, but vendor confirmation is needed.

Exploitation context

The sources describe exploitation through a malicious filesystem and do not cite active exploitation. KEV status is false in the provided bundle. Successful exploitation appears to require high local privilege and a way to influence boot-time filesystem content, making opportunistic internet-scale exploitation unlikely from the available evidence.

Researcher notes

Key uncertainty is exploitability in real deployments, especially where UFS is unused or inaccessible during boot. The public description supports memory corruption and possible Secure Boot bypass, but the bundle does not provide confirmed exploitation, fixed version details for every product, or complete RHEL 7/8 status.

Mitigation direction

  • Apply relevant Red Hat security updates from RHSA-2025:6990 and RHSA-2025:16154 where applicable.
  • Check Red Hat CVE guidance for fixed GRUB2 or RHCOS builds before changing boot components.
  • Prioritize systems where attackers could modify boot media, disks, or hypervisor-provided filesystems.
  • Restrict administrative and physical access to boot paths while remediation is pending.
  • For unknown RHEL 7 and 8 status, monitor vendor guidance and support channels.

Validation and detection

  • Inventory RHEL and OpenShift assets using GRUB2 or RHCOS.
  • Compare installed versions against the affected versions listed in Red Hat advisories.
  • Confirm patched packages are installed and systems have completed required reboot procedures.
  • Review Secure Boot and bootloader configuration after remediation.
  • Track Red Hat advisories for any status change on RHEL 7 or 8.
Prepared
Confidence
high
Sources
7

Based on public source material and reviewed before publication.

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 · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-0677 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
6.4 (3.1)
Known Exploited
No
Published

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

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
6Source 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
6.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H0.55.9redhat

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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 10grub2, 1:2.12-15.el10_0affected
Red HatRed Hat Enterprise Linux 9grub2, 1:2.06-104.el9_6affected
Red HatRed Hat Enterprise Linux 7grub2unknown
Red HatRed Hat Enterprise Linux 8grub2unknown
Red HatRed Hat OpenShift Container Platform 4rhcosaffected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.