CVE-2025-47827: IGEL OS Use of a Key Past its Expiration Date Vulnerability
IGEL OS contains a use of a key past its expiration date vulnerability that allows for Secure Boot bypass. The igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted root filesystem can be mounted from an unverified SquashFS image.
Other sources
In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted root filesystem can be mounted from an unverified SquashFS image.
— MITRE
MITRE CVE-2025-47827: Secure Boot bypass in IGEL OS before 11
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
IGEL IGEL OSto a version that resolves this vulnerability.Fixed in 11 - Compensating control
Follow applicable BOD 22-01 guidance for cloud services.
- Compensating control
Discontinue use of IGEL OS if mitigations are unavailable.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-47827?
CVE-2025-47827 is considered a high severity vulnerability due to its potential to bypass Secure Boot.
How does CVE-2025-47827 affect IGEL OS?
CVE-2025-47827 affects IGEL OS versions prior to 11 by allowing unverified SquashFS images to mount, compromising the system's integrity.
How do I fix CVE-2025-47827?
To fix CVE-2025-47827, upgrade IGEL OS to version 11 or later to ensure proper cryptographic signature verification.
What systems are vulnerable to CVE-2025-47827?
Systems running IGEL OS versions before 11 are vulnerable to CVE-2025-47827 due to the flawed verification in the igel-flash-driver module.
Can CVE-2025-47827 lead to other security issues?
Yes, exploiting CVE-2025-47827 could allow attackers to run malicious code, leading to further security risks within the affected systems.