Loading vulnerability…
A vulnerability in GRUB2 prior to version 2.06 allows the ACPI command to be used even when Secure Boot is enabled. An attacker with privileged access can craft a malicious SSDT that overwrites the Linux kernel lockdown variable in memory. This SSDT is loaded and executed by the kernel, effectively bypassing Secure Boot lockdown and enabling the loading of unsigned code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2020-14372, targeting Linux systems booted with UEFI Secure Boot and GRUB2 (<=2.02). The exploit leverages the ability to load custom ACPI tables via GRUB2, even when Secure Boot is enabled, to patch the kernel's 'kernel_locked_down' flag in memory. The main script, 'genssdt.py', is a Python tool that generates a malicious ACPI SSDT (AML) file. This file, when loaded at boot via GRUB2, disables the kernel lockdown feature, allowing root to load unsigned kernel modules or execute arbitrary code in the kernel, thus bypassing Secure Boot protections. The repository also includes a detailed README explaining the vulnerability, exploitation steps, and usage instructions. The exploit requires root access, KASLR to be disabled, and manual editing of GRUB configuration files to load the generated SSDT. The attack vector is local, as it requires root privileges on the target system.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.