From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 10/20] barebox-tools: upgrade 2026.08.0 -> 2026.09.0
Date: Mon, 21 Sep 2026 08:06:46 +0100 [thread overview]
Message-ID: <20260921070656.521680-10-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260921070656.521680-1-richard.purdie@linuxfoundation.org>
"""
This release fixes vulnerabilities in the FIT image code. Most important
one is fixed with "FIT: resolve FIT images case-sensitively". This
vulnerability allowed to trick barebox into verifying one FIT image node
while booting another. The issue showed up in a security audit and is
fixed in this release, stable updates for v2026.04 and v2026.08 will
follow shortly.
Another issue fixed is that a hash node in a FIT image defines its
algorithm. We used to look only at the first hash node. If that says
crc32 then barebox would use that to verify the image data. This is
changed to iterate over the available algos from strong to weak and
see if one of them can verify the image data. crc32, md5 and sha1 are
explicitly no longer allowed. Note that this vulnerability requires
a signed FIT image with crc32 as hashing algorithm, something a properly
signed FIT image shouldn't have, but as crc32 used to be the
pre-secure-boot standard, it could well have leaked into images.
On the brighter side this release adds support for the Novarq Tactical
1000 board which is a switch built around the Microchip LAN9696. Also
the PXA support has been revived, with the PXA3xx as a fully supported
device tree platform.
"""
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/recipes-bsp/barebox/barebox-common.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-bsp/barebox/barebox-common.inc b/meta/recipes-bsp/barebox/barebox-common.inc
index a9f0593e27f..d94798193b3 100644
--- a/meta/recipes-bsp/barebox/barebox-common.inc
+++ b/meta/recipes-bsp/barebox/barebox-common.inc
@@ -3,6 +3,6 @@ SECTION = "bootloaders"
LIC_FILES_CHKSUM = "file://COPYING;md5=f5125d13e000b9ca1f0d3364286c4192"
-PV = "2026.08.0"
+PV = "2026.09.0"
SRC_URI = "https://barebox.org/download/barebox-${PV}.tar.bz2"
-SRC_URI[sha256sum] = "5b270cbde7f2fc6a78ff6e748eef788bbc04571682e2f2e964cd15a2e009774c"
+SRC_URI[sha256sum] = "491b504c8a79b5a4e30c419b824916b7329bad8abfe34987ba066bafa1fbcfc5"
next prev parent reply other threads:[~2026-09-21 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:06 [PATCH 01/20] ffmpeg: upgrade 9.0.1 -> 9.0.2 Richard Purdie
2026-09-21 7:06 ` [PATCH 02/20] librsvg: upgrade 2.63.0 -> 2.63.2 Richard Purdie
2026-09-21 7:06 ` [PATCH 03/20] python3-dtschema: upgrade 2026.6 -> 2026.9 Richard Purdie
2026-09-21 7:23 ` Patchtest results for " patchtest
2026-09-21 7:06 ` [PATCH 04/20] python3-uv-build: upgrade 0.12.13 -> 0.12.17 Richard Purdie
2026-09-21 7:06 ` [PATCH 05/20] xxhash: upgrade 0.8.3 -> 0.8.4 Richard Purdie
2026-09-21 7:23 ` Patchtest results for " patchtest
2026-09-21 7:06 ` [PATCH 06/20] python3-hatchling: upgrade 1.32.0 -> 1.32.3 Richard Purdie
2026-09-21 7:06 ` [PATCH 07/20] python3-idna: upgrade 3.19 -> 3.20 Richard Purdie
2026-09-21 7:06 ` [PATCH 08/20] python3-pdm: upgrade 2.29.1 -> 2.29.2 Richard Purdie
2026-09-21 7:06 ` [PATCH 09/20] python3-wcwidth: upgrade 0.8.3 -> 0.8.4 Richard Purdie
2026-09-21 7:06 ` Richard Purdie [this message]
2026-09-21 7:06 ` [PATCH 11/20] bind: upgrade 9.20.27 -> 9.20.29 Richard Purdie
2026-09-21 7:06 ` [PATCH 12/20] mesa: upgrade 26.2.2 -> 26.2.3 Richard Purdie
2026-09-21 7:06 ` [PATCH 13/20] python3-pdm-build-locked: upgrade 0.3.7 -> 0.3.8 Richard Purdie
2026-09-21 7:06 ` [PATCH 14/20] python3-vcs-versioning: upgrade 2.4.0 -> 2.4.1 Richard Purdie
2026-09-21 7:06 ` [PATCH 15/20] fastfloat: upgrade 8.2.10 -> 8.3.0 Richard Purdie
2026-09-21 7:06 ` [PATCH 16/20] ppp: upgrade 2.5.3 -> 2.5.4 Richard Purdie
2026-09-21 7:06 ` [PATCH 17/20] python3-urllib3: upgrade 2.7.0 -> 2.8.0 Richard Purdie
2026-09-21 7:06 ` [PATCH 18/20] ruby: upgrade 4.0.6 -> 4.0.7 Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260921070656.521680-10-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox