Six vulnerabilities in the widely used U-Boot bootloader have been discovered that could allow attackers to execute malicious code during device boot, potentially enabling stealthy firmware attacks that compromise security protections and install persistent malware. U-Boot is one of the world's most widely used open-source bootloaders and is found in many embedded Linux devices, including enterprise servers' Baseboard Management Controllers (BMCs), networking equipment, industrial systems, IoT devices, and other appliances. Because U-Boot is responsible for loading the operating system, vulnerabilities in the bootloader can allow attackers to compromise a device before the operating system and its security software have a chance to start. One of its security features, known as Verified Boot, uses cryptographic signatures to ensure that only firmware and operating system images signed by a trusted key are loaded during startup. In a report published this week, firmware security company Binarly disclosed six vulnerabilities in U-Boot's FIT (Flattened Image Tree) signature verification code. "Recognising the critical nature of this component, the Binarly Research team decided to examine the core functionality of the U-Boot project more closely," explains Binarly. "This research revealed six distinct vulnerabilities, ranging in impact from denial of service (DoS) to arbitrary code execution during the verification of an untrusted image." According to the researchers, two of the ...
New U-Boot flaws could enable stealthy firmware attacks
BleepingComputer
·Lawrence Abrams
·Published Jul 10, 2026
·Updated
Affected Software
1 affected component
U-Boot FIT (Flattened Image Tree) signature verification code>=2013.07
Frequently Asked Questions
1
What are the main vulnerabilities discussed in the article?
The article discusses six vulnerabilities in the U-Boot bootloader that could allow attackers to execute malicious code during device boot.
2
What type of attacks can these U-Boot vulnerabilities facilitate?
The vulnerabilities could facilitate stealthy firmware attacks that compromise security and enable the installation of persistent malware.
3
What products are specifically impacted by the identified U-Boot flaws?
The flaws specifically affect the U-Boot FIT signature verification code and U-Boot Verified Boot for firmware image signature verification.
4
When were these U-Boot vulnerabilities discovered and published?
The vulnerabilities were published on July 10, 2026, and are listed in the KEV as exploited on July 13, 2026.
5
What potential security implications do the U-Boot vulnerabilities pose?
The vulnerabilities could undermine security protections in devices and lead to long-term malware persistence.