In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature.
Affects IGEL OS before 11 (IGEL OS 10 with the vulnerable igel-flash-driver module) booting a Microsoft 3rd Party UEFI CA-signed shim. Later versions verify the root filesystem signature.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IGEL OS, the operating system used on IGEL thin client devices, is affected by this vulnerability. An attacker could bypass Secure Boot protections by supplying a manipulated root filesystem, allowing unverified software to load during startup.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- n/a n/a
Version range not reported
References 2
GitHub · Zedeldi/igelfs
GitHub · Zedeldi/CVE-2025-47827
Questions about CVE-2025-47827
What does this mean?
The igel-flash-driver kernel module does not properly check a cryptographic signature, so Secure Boot can be bypassed. A malicious root filesystem can then be mounted and the running kernel replaced through kexec.Source: github.com
Am I affected, and how do I check?
The advisory covers IGEL OS before 11, including IGEL OS 10 with the vulnerable igel-flash-driver kernel module. The affected setup boots a shim signed by the Microsoft 3rd Party UEFI CA, which loads the vulnerable IGEL GRUB and kernel. Check the IGEL OS version and the presence of that kernel module to compare against these conditions.Source: github.com
What should I do about it?
Move to a version that includes the fix, as the advisory states that later versions correctly verify the root filesystem SquashFS signature. Until then, apply the listed workaround of revoking the affected shims through the Secure Boot DBX.Source: github.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-10-14, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data
What if there's no patch?
Revoke the affected shims by updating the Linux Foundation UEFI Revocation dbx to version 20250902 or later. This is the workaround the advisory lists.Source: github.com