Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][scarthgap 0/7] Patch review
Date: Tue,  6 May 2025 08:13:52 -0700	[thread overview]
Message-ID: <cover.1746544207.git.steve@sakoman.com> (raw)

Please review this set of changes for scarthgap and have comments back by
end of day Thursday, May 8

Passed a-full on autobuilder:

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

The following changes since commit 00dd4901e364d16d96cfab864823a9cfdd336eeb:

  Revert "cve-update-nvd2-native: Tweak to work better with NFS DL_DIR" (2025-04-29 10:21:16 -0700)

are available in the Git repository at:

  https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-nut
  https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-nut

Ashish Sharma (1):
  libsoup: patch CVE-2025-46420

Deepesh Varatharajan (2):
  glibc: stable 2.39 branch updates
  binutils: stable 2.42 branch updates

Jeroen Hofstee (2):
  bluez5: make media control a PACKAGECONFIG option
  bluez5: backport a patch to fix btmgmt -i

Peter Marko (1):
  sqlite3: mark CVE-2025-29087 as patched

Soumya Sambu (1):
  elfutils: Fix CVE-2025-1371

 meta/recipes-connectivity/bluez5/bluez5.inc   |  3 +
 ...ndex-option-for-non-interactive-mode.patch | 29 +++++++++
 meta/recipes-core/glibc/glibc-version.inc     |  2 +-
 .../binutils/binutils-2.42.inc                |  2 +-
 .../elfutils/elfutils_0.191.bb                |  1 +
 .../elfutils/files/CVE-2025-1371.patch        | 41 +++++++++++++
 .../libsoup-3.4.4/CVE-2025-46420.patch        | 60 +++++++++++++++++++
 meta/recipes-support/libsoup/libsoup_3.4.4.bb |  1 +
 .../sqlite/sqlite3/CVE-2025-3277.patch        |  1 +
 9 files changed, 138 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5/toolsbtmgmt-fix-index-option-for-non-interactive-mode.patch
 create mode 100644 meta/recipes-devtools/elfutils/files/CVE-2025-1371.patch
 create mode 100644 meta/recipes-support/libsoup/libsoup-3.4.4/CVE-2025-46420.patch

-- 
2.43.0



             reply	other threads:[~2025-05-06 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 15:13 Steve Sakoman [this message]
2025-05-06 15:13 ` [OE-core][scarthgap 1/7] libsoup: patch CVE-2025-46420 Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 2/7] elfutils: Fix CVE-2025-1371 Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 3/7] sqlite3: mark CVE-2025-29087 as patched Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 4/7] glibc: stable 2.39 branch updates Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 5/7] binutils: stable 2.42 " Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 6/7] bluez5: make media control a PACKAGECONFIG option Steve Sakoman
2025-05-06 15:19   ` Gyorgy Sarvari
2025-05-06 15:45     ` Steve Sakoman
2025-05-06 15:13 ` [OE-core][scarthgap 7/7] bluez5: backport a patch to fix btmgmt -i Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2025-12-12 15:39 [OE-core][scarthgap 0/7] Patch review Steve Sakoman
2025-11-04 14:47 Steve Sakoman
2025-05-21 14:59 Steve Sakoman
2025-02-18 21:15 Steve Sakoman
2024-07-09 19: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.1746544207.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