Skip to main content
VulnerabilityPublished Updated

CVE-2024-56738: GNU GRUB2 · Timing Side Channel

Affects GNU GRUB2Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Debiandebian/grub2pkg:deb/debian/grub2Other threatsAffected
  • =2.00
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor official GNU GRUB2 channels and repositories for patches addressing CVE-2024-56738 and apply updates promptly once available.
  2. Until patches are released, consider implementing additional boot security controls such as Trusted Platform Module (TPM)-based measurements and secure boot configurations to reduce exposure.
  3. Restrict network access to systems during the boot process where feasible to limit attacker ability to measure timing discrepancies remotely.
  4. Employ system and network monitoring to detect anomalous timing analysis attempts or unusual bootloader interactions.
  5. For environments using full disk encryption or sensitive bootloader configurations, consider layered encryption or multi-factor authentication mechanisms to mitigate key exposure risks.
  6. Conduct regular security audits of bootloader configurations and cryptographic implementations to identify and remediate potential side-channel vulnerabilities.
  7. Educate system administrators about the risks of timing side-channel attacks and the importance of timely patching and secure boot practices.

Description

GNU GRUB (aka GRUB2) through 2.12 does not use a constant-time algorithm for grub_crypto_memcmp and thus allows side-channel attacks.

References

Community reviews

Loading reviews…