From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/14] Patch review
Date: Sun, 22 Jun 2025 07:59:55 -0700 [thread overview]
Message-ID: <cover.1750604257.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Tuesday, June 24
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1857
The following changes since commit e0857503de9f427d177fe85c32cf0d2748d779fb:
glibc: nptl Use all of g1_start and g_signals (2025-06-17 08:05:29 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Ashish Sharma (1):
libsoup: patch CVE-2025-4476
Changqing Li (8):
libsoup: fix CVE-2025-32907
libsoup: fix CVE-2025-32051
libsoup: fix CVE-2025-46421
libsoup: fix CVE-2025-4948
libsoup-2.4: fix CVE-2025-32907
libsoup-2.4: fix CVE-2025-46421
libsoup-2.4: fix CVE-2025-4948
libsoup-2.4: fix CVE-2025-4476
Hitendra Prajapati (2):
libsoup: Fix CVE-2025-4969
libsoup-2.4: Fix CVE-2025-4969
Moritz Haase (1):
cmake: Correctly handle cost data of tests with arbitrary chars in
name
Peter Marko (1):
go: ignore CVE-2024-3566
Soumya Sambu (1):
systemtap: add sysroot Python paths to configure flags
.../cmake/cmake-native_3.22.3.bb | 2 +-
...trary-characters-in-test-names-of-CT.patch | 205 ++++++++++++++++++
meta/recipes-devtools/cmake/cmake_3.22.3.bb | 1 +
.../go/go-binary-native_1.17.13.bb | 3 +
meta/recipes-devtools/go/go-common.inc | 3 +
.../recipes-kernel/systemtap/systemtap_git.bb | 7 +
.../libsoup/libsoup-2.4/CVE-2025-32907.patch | 39 ++++
.../libsoup/libsoup-2.4/CVE-2025-4476.patch | 38 ++++
.../libsoup/libsoup-2.4/CVE-2025-46421.patch | 47 ++++
.../libsoup/libsoup-2.4/CVE-2025-4948.patch | 38 ++++
.../libsoup/libsoup-2.4/CVE-2025-4969.patch | 76 +++++++
.../libsoup/libsoup-2.4_2.74.2.bb | 5 +
.../libsoup/libsoup/CVE-2025-32051-1.patch | 29 +++
.../libsoup/libsoup/CVE-2025-32051-2.patch | 57 +++++
.../libsoup/libsoup/CVE-2025-32907-1.patch | 200 +++++++++++++++++
.../libsoup/libsoup/CVE-2025-32907-2.patch | 68 ++++++
.../libsoup/libsoup/CVE-2025-4476.patch | 38 ++++
.../libsoup/libsoup/CVE-2025-46421.patch | 139 ++++++++++++
.../libsoup/libsoup/CVE-2025-4948.patch | 97 +++++++++
.../libsoup/libsoup/CVE-2025-4969.patch | 76 +++++++
meta/recipes-support/libsoup/libsoup_3.0.7.bb | 8 +
21 files changed, 1175 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools/cmake/cmake/0001-ctest-Allow-arbitrary-characters-in-test-names-of-CT.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32907.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-4476.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-46421.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-4948.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-4969.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-32051-1.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-32051-2.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-32907-1.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-32907-2.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-4476.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-46421.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-4948.patch
create mode 100644 meta/recipes-support/libsoup/libsoup/CVE-2025-4969.patch
--
2.43.0
next reply other threads:[~2025-06-22 15:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 14:59 Steve Sakoman [this message]
2025-06-22 14:59 ` [OE-core][kirkstone 01/14] libsoup: patch CVE-2025-4476 Steve Sakoman
2025-06-22 14:59 ` [OE-core][kirkstone 02/14] libsoup: Fix CVE-2025-4969 Steve Sakoman
2025-06-22 14:59 ` [OE-core][kirkstone 03/14] libsoup: fix CVE-2025-32907 Steve Sakoman
2025-06-22 14:59 ` [OE-core][kirkstone 04/14] libsoup: fix CVE-2025-32051 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 05/14] libsoup: fix CVE-2025-46421 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 06/14] libsoup: fix CVE-2025-4948 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 07/14] libsoup-2.4: Fix CVE-2025-4969 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 08/14] libsoup-2.4: fix CVE-2025-32907 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 09/14] libsoup-2.4: fix CVE-2025-46421 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 10/14] libsoup-2.4: fix CVE-2025-4948 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 11/14] libsoup-2.4: fix CVE-2025-4476 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 12/14] go: ignore CVE-2024-3566 Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 13/14] systemtap: add sysroot Python paths to configure flags Steve Sakoman
2025-06-22 15:00 ` [OE-core][kirkstone 14/14] cmake: Correctly handle cost data of tests with arbitrary chars in name Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-10-14 22:44 [OE-core][kirkstone 00/14] Patch review Steve Sakoman
2025-04-30 2:53 Steve Sakoman
2024-11-27 18:49 Steve Sakoman
2023-09-06 12:48 Steve Sakoman
2023-03-23 21:04 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.1750604257.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox