Patch review
cover Patch review
Please review this set of changes for scarthgap and have comments back by end of day Friday, October 31
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2655
The following changes since commit 0f98fecda8a0436f760e6fd9f3b7eb510e5258b8:
curl: only set CA bundle in target build (2025-10-24 06:41:43 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-nut
David Nyström (1):
lz4: fix CVE-2025-62813
Hongxu Jia (1):
u-boot: fix CVE-2024-42040
Praveen Kumar (1):
bind: upgrade 9.18.33 -> 9.18.41
Yash Shinde (2):
binutils: fix CVE-2025-11081
binutils: fix CVE-2025-8225
Yogita Urade (1):
tiff: ignore CVE-2025-8961
.../u-boot/files/CVE-2024-42040.patch | 56 +++++++++++++
meta/recipes-bsp/u-boot/u-boot-common.inc | 1 +
.../bind/{bind_9.18.33.bb => bind_9.18.41.bb} | 2 +-
.../binutils/binutils-2.42.inc | 2 +
.../binutils/0026-CVE-2025-11081.patch | 84 +++++++++++++++++++
.../binutils/0027-CVE-2025-8225.patch | 47 +++++++++++
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 2 +-
.../lz4/files/CVE-2025-62813.patch | 73 ++++++++++++++++
meta/recipes-support/lz4/lz4_1.9.4.bb | 5 +-
9 files changed, 268 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-bsp/u-boot/files/CVE-2024-42040.patch
rename meta/recipes-connectivity/bind/{bind_9.18.33.bb => bind_9.18.41.bb} (97%)
create mode 100644 meta/recipes-devtools/binutils/binutils/0026-CVE-2025-11081.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/0027-CVE-2025-8225.patch
create mode 100644 meta/recipes-support/lz4/files/CVE-2025-62813.patchSignature · 1 line
2.43.0
PATCH 1/6 lz4: fix CVE-2025-62813
From: David Nyström <[email protected]>
Prevent attackers to cause a denial of service (application crash) or possibly have unspecified other impact when the application processes untrusted LZ4 frames. For example, LZ4F_createCDict_advanced in lib/lz4frame.c mishandles NULL checks.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2025-62813
Upstream patch:
https://github.com/lz4/lz4/commit/f64efec011c058bd70348576438abac222fe6c82
--- .../lz4/files/CVE-2025-62813.patch | 73 +++++++++++++++++++ meta/recipes-support/lz4/lz4_1.9.4.bb | 5 +- 2 files changed, 76 insertions(+), 2 deletions(-) create mode 100644 meta/recipes-support/lz4/files/CVE-2025-62813.patch
meta/recipes-support/lz4/files/CVE-2025-62813.patch new file +73 -0
@@ -0,0 +1,73 @@ +From 10dbd089b74cf858a24a4aa4c2a438984ddf17d7 Mon Sep 17 00:00:00 2001 +From: louislafosse <[email protected]> +Date: Mon, 31 Mar 2025 20:48:52 +0200 +Subject: [PATCH] fix(null) : improve error handlings when passing a null + pointer to some functions from lz4frame +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +Upstream-Status: Backport [Upstream commit https://github.com/lz4/lz4/commit/f64efec011c058bd70348576438abac222fe6c82] +CVE: CVE-2025-62813 + +Signed-off-by: David Nyström <[email protected]> +--- + lib/lz4frame.c | 15 +++++++++++++-- + tests/frametest.c | 9 ++++++--- + 2 files changed, 19 insertions(+), 5 deletions(-) + +diff --git a/lib/lz4frame.c b/lib/lz4frame.c +index 174f9ae4..cc6ed6f1 100644 +--- a/lib/lz4frame.c ++++ b/lib/lz4frame.c +@@ -530,9 +530,16 @@ LZ4F_CDict* + LZ4F_createCDict_advanced(LZ4F_CustomMem cmem, const void* dictBuffer, size_t dictSize) + { + const char* dictStart = (const char*)dictBuffer; +- LZ4F_CDict* const cdict = (LZ4F_CDict*)LZ4F_malloc(sizeof(*cdict), cmem); ++ LZ4F_CDict* cdict = NULL; ++ + DEBUGLOG(4, "LZ4F_createCDict_advanced"); +- if (!cdict) return NULL; ++ ++ if (!dictStart) ++ return NULL; ++ cdict = (LZ4F_CDict*)LZ4F_malloc(sizeof(*cdict), cmem); ++ if (!cdict) ++ return NULL; ++ + cdict->cmem = cmem; + if (dictSize > 64 KB) { + dictStart += dictSize - 64 KB; +@@ -1429,6 +1436,10 @@ LZ4F_errorCode_t LZ4F_getFrameInfo(LZ4F_dctx* dctx, + LZ4F_frameInfo_t* frameInfoPtr, + const void* srcBuffer, size_t* srcSizePtr) + { ++ assert(dctx != NULL); ++ RETURN_ERROR_IF(frameInfoPtr == NULL, parameter_null); ++ RETURN_ERROR_IF(srcSizePtr == NULL, parameter_null); ++ + LZ4F_STATIC_ASSERT(dstage_getFrameHeader < dstage_storeFrameHeader); + if (dctx->dStage > dstage_storeFrameHeader) { + /* frameInfo already decoded */ +diff --git a/tests/frametest.c b/tests/frametest.c +index 33019551..523e35d1 100644 +--- a/tests/frametest.c ++++ b/tests/frametest.c +@@ -589,10 +589,13 @@ int basicTests(U32 seed, double compressibility) + size_t const srcSize = 65 KB; /* must be > 64 KB to avoid short-size optimizations */ + size_t const dstCapacity = LZ4F_compressFrameBound(srcSize, NULL); + size_t cSizeNoDict, cSizeWithDict; +- LZ4F_CDict* const cdict = LZ4F_createCDict(CNBuffer, dictSize); +- if (cdict == NULL) goto _output_error; +- CHECK( LZ4F_createCompressionContext(&cctx, LZ4F_VERSION) ); ++ LZ4F_CDict* cdict = NULL; + ++ CHECK( LZ4F_createCompressionContext(&cctx, LZ4F_VERSION) ); ++ cdict = LZ4F_createCDict(CNBuffer, dictSize); ++ if (cdict == NULL) ++ goto _output_error; ++ + DISPLAYLEVEL(3, "Testing LZ4F_createCDict_advanced : "); + { LZ4F_CDict* const cda = LZ4F_createCDict_advanced(lz4f_cmem_test, CNBuffer, dictSize); + if (cda == NULL) goto _output_error;
meta/recipes-support/lz4/lz4_1.9.4.bb +3 -2
@@ -13,8 +13,9 @@ PE = "1" SRCREV = "5ff839680134437dbf4678f3d0c7b371d84f4964" SRC_URI = "git://github.com/lz4/lz4.git;branch=release;protocol=https \ - file://run-ptest \ - " + file://run-ptest \ + file://CVE-2025-62813.patch \ + " UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.*)" S = "${WORKDIR}/git"
Signature · 1 line
2.43.0
PATCH 2/6 binutils: fix CVE-2025-11081
In reply to Steve SakomanFrom: Yash Shinde <[email protected]>
CVE: CVE-2025-11081
Trying to dump .sframe in a PE file results in a segfault accessing elf_section_data.
* objdump (dump_sframe_section, dump_dwarf_section): Don't access elf_section_type without first checking the file is ELF.
PR 33406 SEGV in dump_dwarf_section
[https://sourceware.org/bugzilla/show_bug.cgi?id=33406]
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f87a66db645caf8cc0e6fc87b0c28c78a38af59b]
--- .../binutils/binutils-2.42.inc | 1 + .../binutils/0026-CVE-2025-11081.patch | 84 +++++++++++++++++++ 2 files changed, 85 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0026-CVE-2025-11081.patch
meta/recipes-devtools/binutils/binutils-2.42.inc +1 -0
@@ -61,5 +61,6 @@ SRC_URI = "\ file://0023-CVE-2025-7545.patch \ file://0024-CVE-2025-11082.patch \ file://0025-CVE-2025-11083.patch \ + file://0026-CVE-2025-11081.patch \ " S = "${WORKDIR}/git"
meta/recipes-devtools/binutils/binutils/0026-CVE-2025-11081.patch new file +84 -0
84 lines not on this page · raw message
Signature · 1 line
2.43.0
PATCH 3/6 binutils: fix CVE-2025-8225
In reply to Steve SakomanFrom: Yash Shinde <[email protected]>
CVE: CVE-2025-8225
It is possible with fuzzed files to have num_debug_info_entries zero after allocating space for debug_information, leading to multiple allocations.
* dwarf.c (process_debug_info): Don't test num_debug_info_entries to determine whether debug_information has been allocated, test alloc_num_debug_info_entries.
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4]
--- .../binutils/binutils-2.42.inc | 1 + .../binutils/0027-CVE-2025-8225.patch | 47 +++++++++++++++++++ 2 files changed, 48 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0027-CVE-2025-8225.patch
meta/recipes-devtools/binutils/binutils-2.42.inc +1 -0
@@ -62,5 +62,6 @@ SRC_URI = "\ file://0024-CVE-2025-11082.patch \ file://0025-CVE-2025-11083.patch \ file://0026-CVE-2025-11081.patch \ + file://0027-CVE-2025-8225.patch \ " S = "${WORKDIR}/git"
meta/recipes-devtools/binutils/binutils/0027-CVE-2025-8225.patch new file +47 -0
47 lines not on this page · raw message
Signature · 1 line
2.43.0
PATCH 4/6 u-boot: fix CVE-2024-42040
In reply to Steve SakomanFrom: Hongxu Jia <[email protected]>
Backport a patch [1] from upstrem to fix CVE-2024-42040 [2]
[1] https://source.denx.de/u-boot/u-boot/-/commit/81e5708cc2c865df606e49aed5415adb2a662171
[2] https://nvd.nist.gov/vuln/detail/CVE-2024-42040
--- .../u-boot/files/CVE-2024-42040.patch | 56 +++++++++++++++++++ meta/recipes-bsp/u-boot/u-boot-common.inc | 1 + 2 files changed, 57 insertions(+) create mode 100644 meta/recipes-bsp/u-boot/files/CVE-2024-42040.patch
meta/recipes-bsp/u-boot/files/CVE-2024-42040.patch new file +56 -0
@@ -0,0 +1,56 @@ +From 1406fc918977bba4dac0af5e22e63a5553aa6aff Mon Sep 17 00:00:00 2001 +From: Paul HENRYS <[email protected]> +Date: Thu, 9 Oct 2025 17:43:28 +0200 +Subject: [PATCH] net: bootp: Prevent buffer overflow to avoid leaking the RAM + content + +CVE-2024-42040 describes a possible buffer overflow when calling +bootp_process_vendor() in bootp_handler() since the total length +of the packet is passed to bootp_process_vendor() without being +reduced to len-(offsetof(struct bootp_hdr,bp_vend)+4). + +The packet length is also checked against its minimum size to avoid +reading data from struct bootp_hdr outside of the packet length. + +Signed-off-by: Paul HENRYS <[email protected]> +Signed-off-by: Philippe Reynes <[email protected]> + +CVE: CVE-2024-42040 +Upstream-Status: Backport [https://source.denx.de/u-boot/u-boot/-/commit/81e5708cc2c865df606e49aed5415adb2a662171] +Signed-off-by: Hongxu Jia <[email protected]> +--- + net/bootp.c | 11 ++++++++++- + 1 file changed, 10 insertions(+), 1 deletion(-) + +diff --git a/net/bootp.c b/net/bootp.c +index 68002909634..843180d296c 100644 +--- a/net/bootp.c ++++ b/net/bootp.c +@@ -362,6 +362,14 @@ static void bootp_handler(uchar *pkt, unsigned dest, struct in_addr sip, + debug("got BOOTP packet (src=%d, dst=%d, len=%d want_len=%zu)\n", + src, dest, len, sizeof(struct bootp_hdr)); + ++ /* Check the minimum size of a BOOTP packet is respected. ++ * A BOOTP packet is between 300 bytes and 576 bytes big ++ */ ++ if (len < offsetof(struct bootp_hdr, bp_vend) + 64) { ++ printf("Error: got an invalid BOOTP packet (len=%u)\n", len); ++ return; ++ } ++ + bp = (struct bootp_hdr *)pkt; + + /* Filter out pkts we don't want */ +@@ -379,7 +387,8 @@ static void bootp_handler(uchar *pkt, unsigned dest, struct in_addr sip, + + /* Retrieve extended information (we must parse the vendor area) */ + if (net_read_u32((u32 *)&bp->bp_vend[0]) == htonl(BOOTP_VENDOR_MAGIC)) +- bootp_process_vendor((uchar *)&bp->bp_vend[4], len); ++ bootp_process_vendor((uchar *)&bp->bp_vend[4], len - ++ (offsetof(struct bootp_hdr, bp_vend) + 4)); + + net_set_timeout_handler(0, (thand_f *)0); + bootstage_mark_name(BOOTSTAGE_ID_BOOTP_STOP, "bootp_stop"); +-- +2.49.0 +
meta/recipes-bsp/u-boot/u-boot-common.inc +1 -0
@@ -23,6 +23,7 @@ SRC_URI = "git://source.denx.de/u-boot/u-boot.git;protocol=https;branch=master \ file://CVE-2024-57258-2.patch \ file://CVE-2024-57258-3.patch \ file://CVE-2024-57259.patch \ + file://CVE-2024-42040.patch \ " S = "${WORKDIR}/git"
Signature · 1 line
2.43.0
PATCH 5/6 tiff: ignore CVE-2025-8961
In reply to Steve SakomanFrom: Yogita Urade <[email protected]>
This CVE is for the tool which is removed in v4.6.0 via [1] and re-introduced again in v4.7.0 via [2].
[1] https://gitlab.com/libtiff/libtiff/-/commit/eab89a627f0a65e9a1a47c4b30b4802c80b1ac45
[2] https://gitlab.com/libtiff/libtiff/-/commit/9ab54a858049bef020d578c71d82669531551c00
--- meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb +1 -1
@@ -29,7 +29,7 @@ CVE_STATUS[CVE-2015-7313] = "fixed-version: Tested with check from https://secur CVE_STATUS[CVE-2023-3164] = "cpe-incorrect: Issue only affects the tiffcrop tool not compiled by default since 4.6.0" CVE_STATUS_GROUPS += "CVE_STATUS_REMOVED_TOOLS" -CVE_STATUS_REMOVED_TOOLS = "CVE-2024-13978 CVE-2025-8176 CVE-2025-8177 CVE-2025-8534 CVE-2025-8851" +CVE_STATUS_REMOVED_TOOLS = "CVE-2024-13978 CVE-2025-8176 CVE-2025-8177 CVE-2025-8534 CVE-2025-8851 CVE-2025-8961" CVE_STATUS_REMOVED_TOOLS[status] = "cpe-incorrect: tools affected by these CVEs are not present in this release" inherit autotools multilib_header
Signature · 1 line
2.43.0
PATCH 6/6 bind: upgrade 9.18.33 -> 9.18.41
In reply to Steve SakomanFrom: Praveen Kumar <[email protected]>
This upgrade fixes
CVE-2025-8677,CVE-2025-40778 and CVE-2025-40780.
Changelog
==========
https://downloads.isc.org/isc/bind9/9.18.41/doc/arm/html/changelog.html
---
.../bind/{bind_9.18.33.bb => bind_9.18.41.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bind/{bind_9.18.33.bb => bind_9.18.41.bb} (97%)meta/recipes-connectivity/bind/bind_9.18.41.bb renamed from meta/recipes-connectivity/bind/bind_9.18.33.bb +1 -1
@@ -20,7 +20,7 @@ SRC_URI = "https://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.xz \ file://0001-avoid-start-failure-with-bind-user.patch \ " -SRC_URI[sha256sum] = "fb373fac5ebbc41c645160afd5a9fb451918f6c0e69ab1d9474154e2b515de40" +SRC_URI[sha256sum] = "6ddc1d981511c4da0b203b0513af131e5d15e5f1c261145736fe1f35dd1fe79d" UPSTREAM_CHECK_URI = "https://ftp.isc.org/isc/bind9/" # follow the ESV versions divisible by 2
Signature · 1 line
2.43.0