From: Yoann Congal <yoann.congal@smile.fr>
To: openembedded-core@lists.openembedded.org
Cc: Paul Barker <paul@pbarker.dev>
Subject: [OE-core][wrynose 00/27] Pull request (cover letter only)
Date: Sun, 26 Jul 2026 10:17:39 +0200 [thread overview]
Message-ID: <cover.1785049139.git.yoann.congal@smile.fr> (raw)
Those are the patches from the last patch review:
https://lore.kernel.org/all/cover.1784740870.git.yoann.congal@smile.fr/
No review, no change
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4288
meta-intel built with incompatible master branch:
* Green with proper branch: https://autobuilder.yoctoproject.org/valkyrie/#/builders/41/builds/4037
* Patch sent to change default:
[yocto-autobuilder2][PATCH] schedulers: setup wrynose branch for meta-intel
https://lore.kernel.org/yocto-patches/20260726065438.3170266-2-yoann.congal@smile.fr/T/#u
meta-qcom still broken: https://github.com/qualcomm-linux/meta-qcom/issues/2457#issuecomment-5081571633
The following changes since commit b5a6cada82d7ffb362bda9081c354dcc0b6ee264:
openssh: set status for CVE-2026-3497 (2026-07-20 17:24:44 +0200)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/wrynose-next
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/wrynose-next
for you to fetch changes up to 0dfe86a27167689ded394d72ebb5e22157fb9184:
gzip: Fix CVE-2026-41991 (2026-07-21 17:06:45 +0200)
----------------------------------------------------------------
Darsh Kelaiya (1):
gzip: Fix CVE-2026-41991
David Nyström (1):
libssh2: Fix CVE-2025-15661
Deepak Rathore (17):
expat: fix CVE-2026-56403
expat: fix CVE-2026-56408
expat: fix CVE-2026-56404
expat: fix CVE-2026-56405
expat: fix CVE-2026-56410
expat: fix CVE-2026-56406
expat: fix CVE-2026-56409
expat: fix CVE-2026-56411
expat: fix CVE-2026-56407
expat: fix CVE-2026-56132
gnutls: Fix CVE-2026-3832
gnutls: Fix CVE-2026-42009
curl: ignore CVE-2026-4873
curl: fix CVE-2026-5545
curl: fix CVE-2026-6253
curl: fix CVE-2026-6429
libpng: fix CVE-2026-34757
Devansh Patel (7):
openssh: Fix CVE-2026-59999
openssh: Fix CVE-2026-59997
openssh: Fix CVE-2026-59996
openssh: Fix CVE-2026-59995
openssh: Fix CVE-2026-60001
openssh: Fix CVE-2026-60002
openssh: Fix CVE-2026-60000
Peter Marko (1):
glib-2.0: upgrade 2.88.0 -> 2.88.2
.../openssh/openssh/CVE-2026-59995.patch | 44 ++
.../openssh/openssh/CVE-2026-59996.patch | 39 ++
.../openssh/openssh/CVE-2026-59997.patch | 60 ++
.../openssh/openssh/CVE-2026-59999.patch | 38 ++
.../openssh/openssh/CVE-2026-60000.patch | 140 +++++
.../openssh/openssh/CVE-2026-60001.patch | 130 +++++
.../openssh/openssh/CVE-2026-60002.patch | 225 ++++++++
.../openssh/openssh_10.3p1.bb | 7 +
.../expat/expat/CVE-2026-56132_p1.patch | 90 +++
.../expat/expat/CVE-2026-56132_p2.patch | 63 +++
.../expat/expat/CVE-2026-56132_p3.patch | 77 +++
.../expat/expat/CVE-2026-56132_p4.patch | 63 +++
.../expat/expat/CVE-2026-56132_p5.patch | 58 ++
.../expat/expat/CVE-2026-56403_p1.patch | 83 +++
.../expat/expat/CVE-2026-56403_p2.patch | 40 ++
.../expat/expat/CVE-2026-56404.patch | 47 ++
.../expat/expat/CVE-2026-56405.patch | 32 ++
.../expat/CVE-2026-56406-dependent.patch | 58 ++
.../expat/expat/CVE-2026-56406.patch | 37 ++
.../expat/expat/CVE-2026-56407.patch | 44 ++
.../expat/expat/CVE-2026-56408.patch | 36 ++
.../expat/expat/CVE-2026-56409.patch | 53 ++
.../expat/expat/CVE-2026-56410_p1.patch | 40 ++
.../expat/expat/CVE-2026-56410_p2.patch | 41 ++
.../expat/expat/CVE-2026-56411.patch | 47 ++
meta/recipes-core/expat/expat_2.7.5.bb | 17 +
.../glib-2.0/files/CVE-2026-58016-1.patch | 12 +-
.../glib-2.0/files/CVE-2026-58016-2.patch | 30 +-
...l_2.88.0.bb => glib-2.0-initial_2.88.2.bb} | 0
...{glib-2.0_2.88.0.bb => glib-2.0_2.88.2.bb} | 0
meta/recipes-core/glib-2.0/glib.inc | 2 +-
.../gzip/gzip-1.14/CVE-2026-41991.patch | 75 +++
meta/recipes-extended/gzip/gzip_1.14.bb | 1 +
.../libpng/files/CVE-2026-34757_p1.patch | 518 ++++++++++++++++++
.../libpng/files/CVE-2026-34757_p2.patch | 481 ++++++++++++++++
.../libpng/libpng_1.6.56.bb | 4 +-
.../curl/curl/CVE-2026-5545.patch | 43 ++
.../curl/curl/CVE-2026-6253.patch | 389 +++++++++++++
.../curl/curl/CVE-2026-6429-dependent.patch | 81 +++
.../curl/curl/CVE-2026-6429.patch | 325 +++++++++++
meta/recipes-support/curl/curl_8.19.0.bb | 5 +
.../gnutls/gnutls/CVE-2026-3832_p1.patch | 52 ++
.../gnutls/gnutls/CVE-2026-3832_p2.patch | 114 ++++
.../gnutls/gnutls/CVE-2026-42009_p1.patch | 62 +++
.../gnutls/gnutls/CVE-2026-42009_p2.patch | 48 ++
meta/recipes-support/gnutls/gnutls_3.8.12.bb | 4 +
.../libssh2/libssh2/CVE-2025-15661-1.patch | 45 ++
.../libssh2/libssh2/CVE-2025-15661-2.patch | 131 +++++
.../libssh2/libssh2/CVE-2025-15661-3.patch | 57 ++
.../recipes-support/libssh2/libssh2_1.11.1.bb | 3 +
50 files changed, 4068 insertions(+), 23 deletions(-)
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-59995.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-59996.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-59997.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-59999.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-60000.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-60001.patch
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-60002.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p1.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p2.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p3.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p4.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56132_p5.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p1.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56403_p2.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56404.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56405.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406-dependent.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56406.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56407.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56408.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56409.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p1.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56410_p2.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2026-56411.patch
rename meta/recipes-core/glib-2.0/{glib-2.0-initial_2.88.0.bb => glib-2.0-initial_2.88.2.bb} (100%)
rename meta/recipes-core/glib-2.0/{glib-2.0_2.88.0.bb => glib-2.0_2.88.2.bb} (100%)
create mode 100644 meta/recipes-extended/gzip/gzip-1.14/CVE-2026-41991.patch
create mode 100644 meta/recipes-multimedia/libpng/files/CVE-2026-34757_p1.patch
create mode 100644 meta/recipes-multimedia/libpng/files/CVE-2026-34757_p2.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-5545.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6253.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6429-dependent.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2026-6429.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2026-3832_p1.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2026-3832_p2.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2026-42009_p1.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2026-42009_p2.patch
create mode 100644 meta/recipes-support/libssh2/libssh2/CVE-2025-15661-1.patch
create mode 100644 meta/recipes-support/libssh2/libssh2/CVE-2025-15661-2.patch
create mode 100644 meta/recipes-support/libssh2/libssh2/CVE-2025-15661-3.patch
reply other threads:[~2026-07-26 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1785049139.git.yoann.congal@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
/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