From: Yoann Congal <yoann.congal@smile.fr>
To: openembedded-core@lists.openembedded.org
Cc: Paul Barker <paul@pbarker.dev>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [OE-core][scarthgap 00/11] Pull request (cover letter only)
Date: Fri, 28 Aug 2026 10:41:25 +0200 [thread overview]
Message-ID: <cover.1787906349.git.yoann.congal@smile.fr> (raw)
Those are the patches from the last patch review:
https://lore.kernel.org/all/cover.1787652331.git.yoann.congal@smile.fr/
(No changes)
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/4569
The following changes since commit 70dc15941dd33270a92d1001174efb3093e79bdf:
build-appliance-image: Update to scarthgap head revision (2026-08-24 14:28:47 +0100)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-next
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-next
for you to fetch changes up to b7007d82eec734bab6760ae325645ae5b199e384:
rpcbind: Fix CVE-2026-16277 (2026-08-25 07:01:14 +0200)
----------------------------------------------------------------
Adarsh Jagadish Kamini (1):
libssh2: fix CVE-2026-58050
Deepak Rathore (2):
nghttp2: set status for CVE-2026-58055
glib-2.0: fix CVE-2026-58015
Etienne Cordonnier (1):
curl: fix CVE-2025-10148 backport for websockets on 8.7.1
Jaipaul Cheernam (4):
binutils: fix CVE-2025-1147
binutils: fix CVE-2025-8224
binutils: fix CVE-2026-15003
binutils: fix CVE-2026-18220
Peter Marko (1):
bison: patch CVE-2026-56389
Ross Burton (1):
bitbake.conf: add TMPDIR to GIT_CEILING_DIRECTORIES
Vijay Anusuri (1):
rpcbind: Fix CVE-2026-16277
meta/conf/bitbake.conf | 6 +-
.../glib-2.0/glib-2.0/CVE-2026-58015_p1.patch | 97 +++++
.../glib-2.0/glib-2.0/CVE-2026-58015_p2.patch | 55 +++
.../glib-2.0/glib-2.0/CVE-2026-58015_p3.patch | 198 +++++++++
.../glib-2.0/glib-2.0/CVE-2026-58015_p4.patch | 222 ++++++++++
meta/recipes-core/glib-2.0/glib-2.0_2.78.6.bb | 4 +
meta/recipes-core/glib-2.0/glib.inc | 2 +-
.../binutils/binutils-2.42.inc | 4 +
.../binutils/binutils/CVE-2025-1147.patch | 110 +++++
.../binutils/binutils/CVE-2025-8224.patch | 54 +++
.../binutils/binutils/CVE-2026-15003.patch | 400 ++++++++++++++++++
.../binutils/binutils/CVE-2026-18220.patch | 65 +++
.../bison/bison/CVE-2026-56389.patch | 56 +++
meta/recipes-devtools/bison/bison_3.8.2.bb | 1 +
.../rpcbind/rpcbind/CVE-2026-16277.patch | 34 ++
.../recipes-extended/rpcbind/rpcbind_1.2.6.bb | 1 +
.../curl/curl/CVE-2025-10148.patch | 24 +-
.../libssh2/libssh2/CVE-2026-58050.patch | 45 ++
.../recipes-support/libssh2/libssh2_1.11.1.bb | 1 +
.../recipes-support/nghttp2/nghttp2_1.61.0.bb | 2 +
20 files changed, 1367 insertions(+), 14 deletions(-)
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2026-58015_p1.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2026-58015_p2.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2026-58015_p3.patch
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/CVE-2026-58015_p4.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-1147.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-8224.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-15003.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-18220.patch
create mode 100644 meta/recipes-devtools/bison/bison/CVE-2026-56389.patch
create mode 100644 meta/recipes-extended/rpcbind/rpcbind/CVE-2026-16277.patch
create mode 100644 meta/recipes-support/libssh2/libssh2/CVE-2026-58050.patch
next reply other threads:[~2026-08-28 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:41 Yoann Congal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-10 23:08 [OE-core][scarthgap 00/11] Pull request (cover letter only) Yoann Congal
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.1787906349.git.yoann.congal@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).