From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/12] Patch review
Date: Sat, 24 May 2025 06:36:16 -0700 [thread overview]
Message-ID: <cover.1748093626.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Tuesday, May 27
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1647
The following changes since commit e8be08a624b2d024715a5c8b0c37f2345a02336b:
build-appliance-image: Update to kirkstone head revision (2025-05-16 09:00:49 -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-2.4: Fix CVE-2025-46420
Divya Chellam (1):
ruby: fix CVE-2025-27221
Praveen Kumar (2):
connman :fix CVE-2025-32366
glib-2.0: fix CVE-2025-4373
Sundeep KOKKONDA (1):
gcc: AArch64 - Fix strict-align cpymem/setmem
Vijay Anusuri (5):
openssh: Fix CVE-2025-32728
libsoup-2.4: Fix CVE-2025-32910
libsoup-2.4: Fix CVE-2025-32911 & CVE-2025-32913
libsoup-2.4: Fix CVE-2025-32912
libsoup-2.4: Fix CVE-2025-32914
Virendra Thakur (1):
util-linux: Add fix to isolate test fstab entries using CUSTOM_FSTAB
Yi Zhao (1):
iputils: Security fix for CVE-2025-47268
.../connman/connman/CVE-2025-32366.patch | 41 ++
.../connman/connman_1.41.bb | 1 +
.../openssh/openssh/CVE-2025-32728.patch | 44 ++
.../openssh/openssh_8.9p1.bb | 1 +
.../glib-2.0/glib-2.0/CVE-2025-4373-01.patch | 120 +++++
.../glib-2.0/glib-2.0/CVE-2025-4373-02.patch | 29 ++
meta/recipes-core/glib-2.0/glib-2.0_2.72.3.bb | 2 +
meta/recipes-core/util-linux/util-linux.inc | 1 +
.../util-linux/fstab-isolation.patch | 419 ++++++++++++++++++
meta/recipes-devtools/gcc/gcc-11.5.inc | 1 +
...rch64-fix-strict-align-cpymem-setmem.patch | 45 ++
.../ruby/ruby/CVE-2025-27221-0001.patch | 57 +++
.../ruby/ruby/CVE-2025-27221-0002.patch | 73 +++
meta/recipes-devtools/ruby/ruby_3.1.3.bb | 2 +
.../iputils/iputils/CVE-2025-47268.patch | 143 ++++++
.../iputils/iputils_20211215.bb | 1 +
.../libsoup-2.4/CVE-2025-32910-1.patch | 97 ++++
.../libsoup-2.4/CVE-2025-32910-2.patch | 148 +++++++
.../libsoup-2.4/CVE-2025-32910-3.patch | 26 ++
.../CVE-2025-32911_CVE-2025-32913-1.patch | 72 +++
.../CVE-2025-32911_CVE-2025-32913-2.patch | 44 ++
.../libsoup-2.4/CVE-2025-32912-1.patch | 41 ++
.../libsoup-2.4/CVE-2025-32912-2.patch | 30 ++
.../libsoup/libsoup-2.4/CVE-2025-32914.patch | 137 ++++++
.../libsoup/libsoup-2.4/CVE-2025-46420.patch | 60 +++
.../libsoup/libsoup-2.4_2.74.2.bb | 9 +
26 files changed, 1644 insertions(+)
create mode 100644 meta/recipes-connectivity/connman/connman/CVE-2025-32366.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2025-32728.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2025-4373-01.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2025-4373-02.patch
create mode 100644 meta/recipes-core/util-linux/util-linux/fstab-isolation.patch
create mode 100644 meta/recipes-devtools/gcc/gcc/0032-gcc-aarch64-fix-strict-align-cpymem-setmem.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2025-27221-0001.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2025-27221-0002.patch
create mode 100644 meta/recipes-extended/iputils/iputils/CVE-2025-47268.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32910-1.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32910-2.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32910-3.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32911_CVE-2025-32913-1.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32911_CVE-2025-32913-2.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32912-1.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32912-2.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-32914.patch
create mode 100644 meta/recipes-support/libsoup/libsoup-2.4/CVE-2025-46420.patch
--
2.43.0
next reply other threads:[~2025-05-24 13:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 13:36 Steve Sakoman [this message]
2025-05-24 13:36 ` [OE-core][kirkstone 01/12] openssh: Fix CVE-2025-32728 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 02/12] iputils: Security fix for CVE-2025-47268 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 03/12] connman :fix CVE-2025-32366 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 04/12] libsoup-2.4: Fix CVE-2025-46420 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 05/12] libsoup-2.4: Fix CVE-2025-32910 Steve Sakoman
2025-06-03 7:56 ` Kumar, Praveen
2025-06-03 8:53 ` Vijay Anusuri
2025-05-24 13:36 ` [OE-core][kirkstone 06/12] libsoup-2.4: Fix CVE-2025-32911 & CVE-2025-32913 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 07/12] libsoup-2.4: Fix CVE-2025-32912 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 08/12] libsoup-2.4: Fix CVE-2025-32914 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 09/12] glib-2.0: fix CVE-2025-4373 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 10/12] ruby: fix CVE-2025-27221 Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 11/12] util-linux: Add fix to isolate test fstab entries using CUSTOM_FSTAB Steve Sakoman
2025-05-24 13:36 ` [OE-core][kirkstone 12/12] gcc: AArch64 - Fix strict-align cpymem/setmem Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2025-02-18 21:09 [OE-core][kirkstone 00/12] Patch review Steve Sakoman
2022-12-08 22:42 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.1748093626.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.