# CVE-2025-61663: Grub2: missing unregister call for normal commands may lead to use-after-free

> An attacker can trigger a use-after-free in GRUB2's normal command, causing system crashes or potential code execution.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2025
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-70523, AZL-70577, DEBIAN-CVE-2025-61663, GHSA-jf88-7285-jch4, UBUNTU-CVE-2025-61663

## What is CVE-2025-61663?

CVE-2025-61663 is a medium-severity use after free vulnerability in GNU Red Hat Enterprise Linux 10, published on 18 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in the GRUB2 bootloader's normal command that poses an immediate Denial of Service (DoS) risk. This flaw is a Use-after-Free issue, caused because the normal command is not properly unregistered when the module is unloaded. An attacker who can execute this command can force the system to access memory locations that are no longer valid. Successful exploitation leads directly to system instability, which can result in a complete crash and halt system availability. Impact on the data integrity and confidentiality is also not discarded.

Weakness: CWE-825 (Expired Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-61663 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61663 is a medium-severity use after free vulnerability in GNU Red Hat Enterprise Linux 10, published on 18 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61663 in the wild and no public exploit code.

Affected product: GNU 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-61663/ (Markdown: https://insights.sbomify.com/CVE-2025-61663/index.md)
```

## Sources

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

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