# CVE-2025-0622: Grub2: command/gpg: use-after-free due to hooks not being removed on module unload

> Attackers can exploit a use-after-free in GRUB2 to execute arbitrary code and bypass Secure Boot protections.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110406, BELL-CVE-2025-0622, DEBIAN-CVE-2025-0622, GHSA-vjmw-pmxv-8c6w, UBUNTU-CVE-2025-0622

## What is CVE-2025-0622?

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

### Official description

A flaw was found in command/gpg. In some scenarios, hooks created by loaded modules are not removed when the related module is unloaded. This flaw allows an attacker to force grub2 to call the hooks once the module that registered it was unloaded, leading to a use-after-free vulnerability. If correctly exploited, this vulnerability may result in arbitrary code execution, eventually allowing the attacker to bypass secure boot protections.

Weakness: CWE-416 (Use After Free)

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


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

Apply the vendor's patch.

## Is CVE-2025-0622 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0622 is a medium-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 18 Feb 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-0622 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-0622/ (Markdown: https://insights.sbomify.com/CVE-2025-0622/index.md)
```

## Sources

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

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