public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/6] Patch review
Date: Mon, 10 Mar 2025 06:36:18 -0700	[thread overview]
Message-ID: <cover.1741613667.git.steve@sakoman.com> (raw)

Please review this set of changes for kirkstone and have comments back by
end of day Wednesday, March 12

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1152

The following changes since commit 0d9f2fcc2058407eb138297d9f8f12595851b963:

  mesa: Fix missing GLES3 headers in SDK sysroot (2025-03-04 08:43:39 -0800)

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

Alessio Cascone (1):
  tzcode-native: Fix compiler setting from 2023d version

Deepesh Varatharajan (1):
  binutils: Fix CVE-2025-0840

Hitendra Prajapati (1):
  ruby: Fix CVE-2025-27220

Priyal Doshi (1):
  tzdata/tzcode-native: upgrade 2024b -> 2025a

Vijay Anusuri (2):
  openssh: Fix CVE-2025-26465
  libtasn1: upgrade 4.19.0 -> 4.20.0

 .../openssh/openssh/CVE-2025-26465.patch      | 140 ++++++++++++++++++
 .../openssh/openssh_8.9p1.bb                  |   1 +
 .../binutils/binutils-2.38.inc                |   1 +
 .../binutils/0038-CVE-2025-0840.patch         |  53 +++++++
 .../ruby/ruby/CVE-2025-27220.patch            |  76 ++++++++++
 meta/recipes-devtools/ruby/ruby_3.1.3.bb      |   1 +
 meta/recipes-extended/timezone/timezone.inc   |   6 +-
 .../timezone/tzcode-native.bb                 |   2 +-
 ...{libtasn1_4.19.0.bb => libtasn1_4.20.0.bb} |   7 +-
 9 files changed, 279 insertions(+), 8 deletions(-)
 create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2025-26465.patch
 create mode 100644 meta/recipes-devtools/binutils/binutils/0038-CVE-2025-0840.patch
 create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2025-27220.patch
 rename meta/recipes-support/gnutls/{libtasn1_4.19.0.bb => libtasn1_4.20.0.bb} (63%)

-- 
2.43.0



             reply	other threads:[~2025-03-10 13:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 13:36 Steve Sakoman [this message]
2025-03-10 13:36 ` [OE-core][kirkstone 1/6] openssh: Fix CVE-2025-26465 Steve Sakoman
2025-03-10 13:36 ` [OE-core][kirkstone 2/6] binutils: Fix CVE-2025-0840 Steve Sakoman
2025-03-10 13:36 ` [OE-core][kirkstone 3/6] ruby: Fix CVE-2025-27220 Steve Sakoman
2025-03-10 13:36 ` [OE-core][kirkstone 4/6] libtasn1: upgrade 4.19.0 -> 4.20.0 Steve Sakoman
2025-03-10 13:36 ` [OE-core][kirkstone 5/6] tzdata/tzcode-native: upgrade 2024b -> 2025a Steve Sakoman
2025-03-10 13:36 ` [OE-core][kirkstone 6/6] tzcode-native: Fix compiler setting from 2023d version Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2025-05-09 16:16 [OE-core][kirkstone 0/6] Patch review Steve Sakoman
2025-03-24 19:36 Steve Sakoman
2024-09-05 12:40 Steve Sakoman
2024-08-25 18:49 Steve Sakoman
2024-07-20 12:42 Steve Sakoman
2024-05-13 12:18 Steve Sakoman
2024-01-21 18:57 Steve Sakoman
2024-01-08 16:14 Steve Sakoman
2023-10-21 15:28 Steve Sakoman
2023-04-05  2: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.1741613667.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