Description
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.
Published: 2026-10-02
Score: 6.4 Medium
EPSS: n/a
KEV: No
Impact: Privilege Escalation
Action: Immediate Patch
AI Analysis

Impact

A local attacker who can modify GRUB’s configuration can bypass the Secure Boot lockdown restriction by supplying an invalid MMIO base address to the serial command. The lack of validation lets GRUB write to an attacker‑controlled memory location, resetting the grub_file_verifiers list and disabling verification of subsequently loaded modules. This effectively allows the attacker to load and execute unsigned GRUB modules during the boot process, providing a path to execute arbitrary code with full system privileges. The weakness is identified as CWE‑822.

Affected Systems

The vulnerability affects GNU Grub2. No specific version range is enumerated, but any instance that includes the serial command while booting in Secure Boot mode is susceptible. The documented fix is in commit 26beaa3b from the GNU Grub project.

Risk and Exploitability

The CVSS score of 6.4 indicates a medium risk level, and the EPSS score is unavailable. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires local access to modify GRUB configuration before the system boots, making the attack likely limited to scenarios where an attacker has physical or otherwise privileged access to the boot media. To succeed, the attacker must supply an MMIO base address that does not correspond to a UART device, which suffices to disable module verification and enable unsigned module execution.

Generated by OpenCVE AI on October 2, 2026 at 11:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest GNU Grub2 release that incorporates commit 26beaa3b, which validates MMIO base addresses for the serial command in Secure Boot mode.
  • If a patch is not yet available, remove any custom serial MMIO base address configuration or restrict access to GRUB configuration files so only authorized users can modify them.
  • Disable or remove the serial command from the GRUB configuration to prevent it from using arbitrary MMIO base addresses during Secure Boot.

Generated by OpenCVE AI on October 2, 2026 at 11:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 02 Oct 2026 11:45:00 +0000

Type Values Removed Values Added
First Time appeared Gnu
Gnu grub2
Vendors & Products Gnu
Gnu grub2

Fri, 02 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Bypass of GRUB lockdown restriction in Secure Boot mode via serial command MMIO base address
Weaknesses CWE-822
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: canonical

Published:

Updated: 2026-10-02T10:34:23.314Z

Reserved: 2026-09-25T08:49:34.867Z

Link: CVE-2026-97876

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-02T11:17:39.727

Modified: 2026-10-02T11:17:39.727

Link: CVE-2026-97876

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-02T12:00:15Z

Weaknesses
  • CWE-822

    Untrusted Pointer Dereference