# CVE-2025-0690: Grub2: read: integer overflow may lead to out-of-bounds write

> An integer overflow in GRUB2's read command allows heap out-of-bounds writes, potentially enabling secure boot bypass or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Feb 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-57150, AZL-57159, BELL-CVE-2025-0690, DEBIAN-CVE-2025-0690, GHSA-9fg2-2f57-9p5h, UBUNTU-CVE-2025-0690

## What is CVE-2025-0690?

CVE-2025-0690 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 24 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The read command is used to read the keyboard input from the user, while reads it keeps the input length in a 32-bit integer value which is further used to reallocate the line buffer to accept the next character. During this process, with a line big enough it's possible to make this variable to overflow leading to a out-of-bounds write in the heap based buffer. This flaw may be leveraged to corrupt grub's internal critical data and secure boot bypass is not discarded as consequence.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-0690?


## How do I fix CVE-2025-0690?

Apply the vendor's patch.

## Is CVE-2025-0690 being exploited?

There is no known exploitation of CVE-2025-0690 in the wild and no public exploit code.

Public exploit code:

- https://github.com/kaleth4/CVE-2025-0690 (github_poc): https://github.com/kaleth4/CVE-2025-0690

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0690 and fix it if it is affected.

What it is: CVE-2025-0690 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 24 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0690 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0690/ (Markdown: https://insights.sbomify.com/CVE-2025-0690/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0690
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0690
- OSV: https://osv.dev/vulnerability/CVE-2025-0690

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0690/
Summaries are generated and may contain mistakes; the official description above is the record.