A local attacker with control over the configuration can bypass lockdown restrictions during Secure Boot to load an unsigned module. The issue stems from insufficient validation of the MMIO (Memory-Mapped I/O) base address passed to the GRUB serial command. Because GRUB fails to verify that the base address corresponds to a UART (Universal Asynchronous Receiver-Transmitter) device, an attacker can provide an arbitrary memory address. This allows the attacker to write data to a controlled address and reset the `grub file verifiers` list, which disables the verification of subsequently loaded modules while the system still reports that lockdown is enabled.