Secure-boot bypass via ambiguous FIT node lookup
Published Feb 17, 2021 · Updated Nov 3, 2025
Secure-boot bypass in Das U-Boot before 2021.04-rc2 allows attackers to load an unintended FIT image through a crafted node name. libfdt treats a node's unit-address suffix as optional during lookup, so a reference such as kernel can resolve to a different kernel@1 node. Exploitation requires a crafted FIT to reach local boot processing and user interaction, after which signature checks can apply to the wrong image.
Summary
What happened
Secure-boot bypass in Das U-Boot before 2021.04-rc2 allows attackers to load an unintended FIT image through a crafted node name. libfdt treats a node's unit-address suffix as optional during lookup, so a reference such as kernel can resolve to a different kernel@1 node. Exploitation requires a crafted FIT to reach local boot processing and user interaction, after which signature checks can apply to the wrong image.
The record
- CVE
- CVE-2021-27138
- Published
- Feb 17, 2021
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1553.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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