commit | 73315f7b51b148eed238c8fc51cea92a06fc082f | [log] [tgz] |
---|---|---|
author | Thomas Altenbach <thomas.altenbach@legrand.com> | Thu Apr 04 13:46:38 2024 +0200 |
committer | David Brown <davidb@davidb.org> | Tue Apr 23 11:03:22 2024 -0600 |
tree | e5c5e420e0f078f2945eb7950218ede1c9932670 | |
parent | 453096b17ddc3aac7bf6afb97c40591d5ea3aa9c [diff] |
bootutil: Fix memory leak in HKDF implementation The bootutil_hmac_sha256_set_key routine performs some dynamic memory allocations when mbedTLS is used. To properly free the allocated memory, bootutil_hmac_sha256_drop must be called before reinitializing the HMAC context using bootutil_hmac_sha256_init. However, in the hkdf routine, the HMAC context was freed only once even though it was initialized multiple times. Signed-off-by: Thomas Altenbach <thomas.altenbach@legrand.com>
This is MCUboot version 2.1.0-dev
MCUboot is a secure bootloader for 32-bits microcontrollers. It defines a common infrastructure for the bootloader and the system flash layout on microcontroller systems, and provides a secure bootloader that enables easy software upgrade.
MCUboot is not dependent on any specific operating system and hardware and relies on hardware porting layers from the operating system it works with. Currently, MCUboot works with the following operating systems and SoCs:
RIOT is supported only as a boot target. We will accept any new port contributed by the community once it is good enough.
See the following pages for instructions on using MCUboot with different operating systems and SoCs:
There are also instructions for the Simulator.
The issues being planned and worked on are tracked using GitHub issues. To give your input, visit MCUboot GitHub Issues.
You can find additional documentation on the bootloader in the source files. For more information, use the following links:
Developers are welcome!
Use the following links to join or see more about the project: