Boot failure via malformed LogError invocation
Published Jan 29, 2024 · Updated Nov 20, 2025
NULL pointer dereference in Red Hat Shim allows local users to crash the UEFI bootloader while it creates an ESL variable. The error path in mok.c calls LogError() with arguments that do not match its format string, causing a read from address zero. Triggering requires local access and an ESL-variable creation failure; the fault interrupts boot, with no confidentiality or integrity impact reported.
Summary
What happened
NULL pointer dereference in Red Hat Shim allows local users to crash the UEFI bootloader while it creates an ESL variable. The error path in mok.c calls LogError() with arguments that do not match its format string, causing a read from address zero. Triggering requires local access and an ESL-variable creation failure; the fault interrupts boot, with no confidentiality or integrity impact reported.
The record
- CVE
- CVE-2023-40546
- Published
- Jan 29, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo