cve.bz

CVE-2026-97876 gnu grub2: Untrusted Pointer Dereference

6.4 mediumEPSS 0.1%

Medium (6.4) in gnu grub2. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB module, while GRUB continues to report lockdown is enabled. The vulnerability is caused by insufficient validation of the MMIO base address passed to the GRUB serial command. GRUB does not validate that the base address corresponds to a UART device, rather than being an arbitrary memory address. This allows an attacker to trick GRUB into writing non-arbitrary data at an attacker-controlled address, including resetting the grub_file_verifiers list in a way that disables the subsequent verification of loaded modules.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-822 Untrusted Pointer Dereference
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-97876 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97876?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97876?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97876 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-97876

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-97876](https://cve.bz/cve/badge/CVE-2026-97876.svg)](https://cve.bz/cve/CVE-2026-97876)

HTML:

<a href="https://cve.bz/cve/CVE-2026-97876"><img src="https://cve.bz/cve/badge/CVE-2026-97876.svg" alt="CVE-2026-97876"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GNU grub2from 2.12 before 2.16

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13grub2no fix listedDEBIAN-CVE-2026-97876
Debian14grub22.14-4DEBIAN-CVE-2026-97876
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moregrub2-signed, grub2-unsignedno fix listedUBUNTU-CVE-2026-97876
UbuntuPro:14.04:LTSgrub2, grub2-signedno fix listedUBUNTU-CVE-2026-97876
Alpaquita23grub2.12-r9BELL-CVE-2026-97876
Alpaquita25grub2.12-r12BELL-CVE-2026-97876
Alpaquitastreamgrub2.14-r2BELL-CVE-2026-97876

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

There is no complete mitigation for this issue other than applying a fixed GRUB build; the underlying fix requires validating the UART/MMIO resource used by the serial command and making the module-verification path fail closed when the verifier list is empty under lockdown.

Until a fixed build is available, exposure can be reduced by:

- Restricting who can modify or supply GRUB boot configuration (grub.cfg) and disallowing untrusted or attacker-controlled removable boot media.

- Avoiding use of the serial console/terminal_input during boot on systems relying on Secure Boot lockdown, where serial input is not otherwise required.

- Treating administrator-level control over boot configuration as equivalent to the ability to bypass lockdown module verification on affected GRUB builds, and applying the same access controls accordingly.

These steps reduce the attack surface but do not close the underlying validation flaw; they do not help if the attacker already controls boot configuration or removable boot media.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10grub2Fix deferred
Red Hat Enterprise Linux 7grub2Fix deferred
Red Hat Enterprise Linux 8grub2Fix deferred
Red Hat Enterprise Linux 9grub2Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97876.

Attack patterns (CAPEC)

  • CAPEC-129 Pointer Manipulation Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON