# CVE-2025-0624: Grub2: net: out-of-bounds write in grub_net_search_config_file() > An out-of-bounds write in GRUB2 during network boot allows remote code execution and secure boot bypass via crafted environment variables. - **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:C/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:** 19 Feb 2025 - **Updated:** 13 Oct 2026 - **Also known as:** ALSA-2025:2867, ALSA-2025:3367, AZL-56997, AZL-57049, BELL-CVE-2025-0624, CLSA-2025-1756231459, DEBIAN-CVE-2025-0624, GHSA-q3rr-g46f-jgqr, RHSA-2025:2521, RHSA-2025:2653, RHSA-2025:2655, RHSA-2025:2675, RHSA-2025:2784, RHSA-2025:2799, RHSA-2025:2867, RHSA-2025:2869, RHSA-2025:3367, RHSA-2025:3396, RLSA-2025:2867, RLSA-2025:3367, UBUNTU-CVE-2025-0624 ## What is CVE-2025-0624? CVE-2025-0624 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 19 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 grub2. During the network boot process, when trying to search for the configuration file, grub copies data from a user controlled environment variable into an internal buffer using the grub_strcpy() function. During this step, it fails to consider the environment variable length when allocating the internal buffer, resulting in an out-of-bounds write. If correctly exploited, this issue may result in remote code execution through the same network segment grub is searching for the boot information, which can be used to by-pass secure boot protections. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2025-0624? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `grub2-common` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-aa64` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-aa64-cdboot` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-aa64-modules` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-ia32` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-ia32-cdboot` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-ia32-modules` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-x64` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-x64-cdboot` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-efi-x64-modules` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-pc` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-pc-modules` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-ppc64le` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-ppc64le-modules` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-tools` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-tools-efi` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-tools-extra` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-tools-minimal` | AlmaLinux:8 | All versions | 1:2.02-162.el8_10.alma.1 | | `grub2-common` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-aa64` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-aa64-cdboot` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-aa64-modules` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-x64` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-x64-cdboot` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-efi-x64-modules` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-pc` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-pc-modules` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-ppc64le` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-ppc64le-modules` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-tools` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-tools-efi` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-tools-extra` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2-tools-minimal` | AlmaLinux:9 | All versions | 1:2.06-94.el9_5.alma.1 | | `grub2` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-common` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-efi-aa64` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-efi-aa64-cdboot` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | | `grub2-efi-aa64-modules` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.02-162.el8_10 | ## How do I fix CVE-2025-0624? Apply the vendor's patch. ## Is CVE-2025-0624 being exploited? There is no known exploitation of CVE-2025-0624 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-0624 and fix it if it is affected. What it is: CVE-2025-0624 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 19 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-0624 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-0624/ (Markdown: https://insights.sbomify.com/CVE-2025-0624/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0624 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0624 - OSV: https://osv.dev/vulnerability/CVE-2025-0624 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-0624/ Summaries are generated and may contain mistakes; the official description above is the record.