From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][scarthgap 0/7] Patch review
Date: Tue, 4 Nov 2025 06:47:51 -0800 [thread overview]
Message-ID: <cover.1762267481.git.steve@sakoman.com> (raw)
Please review this set of changes for scarthgap and have comments back by
end of day Thursday, November 6
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2676
The following changes since commit 4cb834388759540ea5bf7265389b9f1b2e15333a:
bind: upgrade 9.18.33 -> 9.18.41 (2025-10-29 07:13:09 -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
Bastian Krause (1):
util-linux: fix pointer usage in hwclock param handling
Michael Haener (1):
Remove empty file
Peter Marko (4):
wpa-supplicant: patch CVE-2025-24912
binutils: patch CVE-2025-11414
binutils: patch CVE-2025-11412
binutils: patch CVE-2025-11413
Yannic Moog (1):
perf: add arm64 source files for unistd_64.h
.../wpa-supplicant/CVE-2025-24912-01.patch | 79 +++++++++++++++++
.../wpa-supplicant/CVE-2025-24912-02.patch | 70 ++++++++++++++++
.../wpa-supplicant/wpa-supplicant_2.10.bb | 2 +
meta/recipes-core/util-linux/util-linux.inc | 1 +
...-utils-hwclock-rtc-fix-pointer-usage.patch | 27 ++++++
.../binutils/binutils-2.42.inc | 3 +
.../binutils/binutils/CVE-2025-11412.patch | 35 ++++++++
.../binutils/binutils/CVE-2025-11413.patch | 38 +++++++++
.../binutils/binutils/CVE-2025-11414.patch | 84 +++++++++++++++++++
meta/recipes-kernel/perf/perf.bb | 3 +-
test | 0
11 files changed, 341 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2025-24912-01.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2025-24912-02.patch
create mode 100644 meta/recipes-core/util-linux/util-linux/sys-utils-hwclock-rtc-fix-pointer-usage.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-11412.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-11413.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-11414.patch
delete mode 100644 test
--
2.43.0
next reply other threads:[~2025-11-04 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 14:47 Steve Sakoman [this message]
2025-11-04 14:47 ` [OE-core][scarthgap 1/7] wpa-supplicant: patch CVE-2025-24912 Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 2/7] binutils: patch CVE-2025-11414 Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 3/7] binutils: patch CVE-2025-11412 Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 4/7] binutils: patch CVE-2025-11413 Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 5/7] Remove empty file Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 6/7] util-linux: fix pointer usage in hwclock param handling Steve Sakoman
2025-11-04 14:47 ` [OE-core][scarthgap 7/7] perf: add arm64 source files for unistd_64.h Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-12-12 15:39 [OE-core][scarthgap 0/7] Patch review Steve Sakoman
2025-05-21 14:59 Steve Sakoman
2025-05-06 15:13 Steve Sakoman
2025-02-18 21:15 Steve Sakoman
2024-07-09 19:29 Steve Sakoman
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=cover.1762267481.git.steve@sakoman.com \
--to=steve@sakoman.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.