# CVE-2025-54771: Grub2: use-after-free in grub_file_close()

> An attacker can exploit a use-after-free flaw in the GRUB bootloader to cause a system crash or potentially compromise data integrity and confidentiality.

- **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:** DEBIAN-CVE-2025-54771, GHSA-5rr4-3f6q-m7hp, UBUNTU-CVE-2025-54771

## What is CVE-2025-54771?

CVE-2025-54771 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 use-after-free vulnerability has been identified in the GNU GRUB (Grand Unified Bootloader). The flaw occurs because the file-closing process incorrectly retains a memory pointer, leaving an invalid reference to a file system structure. An attacker could exploit this vulnerability to cause grub to crash, leading to a Denial of Service. Possible data integrity or confidentiality compromise is not discarded.

Weakness: CWE-825 (Expired Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-54771 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54771 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-54771 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-54771/ (Markdown: https://insights.sbomify.com/CVE-2025-54771/index.md)
```

## Sources

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

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