Security readout for executives and security teams
Plain-English summary
CVE-2025-1125 is a GRUB2 bootloader flaw triggered by a maliciously crafted HFS filesystem. If a system is made to read that filesystem during boot, memory corruption could allow code execution and potentially bypass Secure Boot. Public sources do not show active exploitation, and Red Hat currently lists its named products as unaffected.
Executive priority
Treat as a high-priority boot-chain issue for fleets using GRUB2, especially endpoints, kiosks, labs, and servers with local media exposure. Do not assume impact across all Linux systems; confirm vendor status. Red Hat-listed products in the provided source are marked unaffected.
Technical view
GRUB2’s HFS filesystem handling uses filesystem-controlled metadata in buffer size calculations without adequate integer-overflow checks. Overflow can cause an undersized grub_malloc allocation, followed by a heap out-of-bounds write in hfsplus_open_compressed_real(). The CVSS is 7.8: local attack vector, low complexity, no privileges, user interaction required, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most relevant where GRUB2 can process attacker-controlled HFS or HFS+ filesystems, such as removable media, disk images, or boot paths influenced by local access. Red Hat’s CVE page marks listed RHEL and OpenShift Container Platform entries as unaffected. Other GRUB2 downstreams require vendor-specific confirmation.
Exploitation context
The source bundle reports no CISA KEV listing and provides no cited evidence of active exploitation. Exploitation requires local conditions and user interaction: the bootloader must read a crafted HFS filesystem. Successful exploitation could corrupt GRUB internals and may bypass Secure Boot protections.
Researcher notes
Key weakness is CWE-787 from integer overflow in HFS buffer sizing. The reported vulnerable path is hfsplus_open_compressed_real(), producing a heap out-of-bounds write after undersized allocation. Public evidence in the bundle does not include exploitation details or a universal upstream fix statement, so downstream advisories are essential.
Mitigation direction
- Check your OS or appliance vendor advisory for affected GRUB2 builds and fixes.
- Prioritize systems that boot from or inspect removable or user-supplied media.
- Restrict unauthorized physical access and untrusted boot media where feasible.
- Confirm whether your distribution marks its GRUB2 packages affected or unaffected.
- Apply vendor-provided GRUB2, shim, or bootloader updates if issued.
Validation and detection
- Inventory systems using GRUB2 in the boot chain.
- Check vendor CVE status for each distribution and appliance image.
- Determine whether GRUB2 HFS filesystem support is present or enabled.
- Review boot policies for removable, external, or user-controlled media.
- Verify Secure Boot update guidance from the platform vendor.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupContainer 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 lookupCVE-2025-1125 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9redhatVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2025-1125CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2346138CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://lists.gnu.org/archive/html/grub-devel/2025-02/msg00024.htmlCVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.