dbcve.org
Grub2Application · Gnu

CVE-2024-2312

MEDIUM · 6.7 CVSS v3.1 Published 2024-04-05
Fix available
A fix is available. Upgrade to 2.12-1ubuntu5 or later.
See remediation →
69/100
Remediation priority · Elevated
Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GRUB2 does not call the module fini functions on exit, leading to Debian/Ubuntu's peimage GRUB2 module leaving UEFI system table hooks after exit. This lead to a use-after-free condition, and could possibly lead to secure boot bypass.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Grub2Application
Affected:< 2.12-1ubuntu5
Bootstrap OsOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.12-1ubuntu5 or later
Fixed in 2.12-1ubuntu5
Vendor patch bugs.launchpad.net →
Recommended fix High confidence

GRUB2 version 2.12-1ubuntu5 or later

  1. 1. Identify the current GRUB2 version installed on the system using: `grub2-install --version` or `dpkg -l | grep grub2`
  2. 2. Update the package manager cache: `sudo apt update` (for Debian/Ubuntu-based systems)
  3. 3. Upgrade GRUB2 to the fixed version: `sudo apt install grub2` or `sudo apt upgrade grub2`
  4. 4. Verify the installed version is >= 2.12-1ubuntu5 using: `dpkg -l | grep grub2`
  5. 5. Reinstall GRUB2 to EFI partition if needed: `sudo grub-install /dev/sdX` (replace X with appropriate device)
  6. 6. If using UEFI Secure Boot, re-sign GRUB2 with sbctl or mokutil according to your distribution's procedures
  7. 7. Reboot the system to load the updated GRUB2
Caveat Upgrading GRUB2 may require reconfiguration of custom menu entries and re-signing for Secure Boot; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2312 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data