Secure Boot bypass via read-buffer integer overflow
Published Feb 24, 2025 · Updated Jul 8, 2026
Heap out-of-bounds write in GNU GRUB 2.12 and earlier allows physically proximate attackers to corrupt boot-loader memory via keyboard input. The read command stores input length in a 32-bit integer and reuses the overflowing value to resize its heap line buffer before accepting another character. Reaching the flaw requires high privileges, physical access, and user interaction; corruption of GRUB's critical data can undermine Secure Boot integrity.
Summary
What happened
Heap out-of-bounds write in GNU GRUB 2.12 and earlier allows physically proximate attackers to corrupt boot-loader memory via keyboard input. The read command stores input length in a 32-bit integer and reuses the overflowing value to resize its heap line buffer before accepting another character. Reaching the flaw requires high privileges, physical access, and user interaction; corruption of GRUB's critical data can undermine Secure Boot integrity.
The record
- CVE
- CVE-2025-0690
- Published
- Feb 24, 2025
- Updated
- Jul 8, 2026
- Vendor
- The GnuPG Project
- Product
- GNU GRUB
- Classifications
- CWE-787, T1547.001
- Attack vector
- physical
- Privileges
- admin
Timeline
How it unfolded
- Feb 24, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo