public inbox for openembedded-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/7] Scarthgap pull request
Date: Sun,  5 Apr 2026 18:57:06 +0530	[thread overview]
Message-ID: <cover.1775370794.git.anuj.mittal@oss.qualcomm.com> (raw)

Please merge these changes in scarthgap. Tested locally and on
autobuilder.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/81/builds/1435

The following changes since commit 06f846a325fde423bb0a6d49d771d8c1e144d7eb:

  bluealsa: fix QA issue staticdev (2026-03-24 15:53:24 +0530)

are available in the Git repository at:

  https://git.openembedded.org/meta-openembedded-contrib anujm/scarthgap
  https://git.openembedded.org/meta-openembedded-contrib/log/?h=anujm/scarthgap

for you to fetch changes up to 1ad0d777d1de1769e5995eb806f7ae5c15d0be54:

  strongswan: Fix CVE-2026-25075 (2026-04-03 15:00:48 +0530)

----------------------------------------------------------------

Hitendra Prajapati (1):
  python3-cbor2: patch CVE-2026-26209

Markus Volk (1):
  flatpak: add PACKAGECONFIG for dconf

Martin Jansa (1):
  freerdp: remove 0001-Fix-const-qualifier-error.patch

Vijay Anusuri (4):
  libssh: Fix CVE-2026-0964
  libssh: Fix CVE-2026-0966
  giflib: Fix CVE-2026-23868
  strongswan: Fix CVE-2026-25075

 .../strongswan/CVE-2026-25075.patch           |  50 ++
 .../strongswan/strongswan_5.9.14.bb           |   1 +
 .../giflib/giflib/CVE-2026-23868.patch        |  34 ++
 .../recipes-devtools/giflib/giflib_5.2.2.bb   |   1 +
 .../flatpak/flatpak_1.15.8.bb                 |   3 +-
 .../0001-Fix-const-qualifier-error.patch      |  57 ---
 .../recipes-support/freerdp/freerdp_2.11.8.bb |   1 -
 .../libssh/libssh/CVE-2026-0964.patch         |  46 ++
 .../libssh/libssh/CVE-2026-0966-1.patch       |  35 ++
 .../libssh/libssh/CVE-2026-0966-2.patch       |  71 +++
 .../libssh/libssh/CVE-2026-0966-3.patch       |  65 +++
 .../recipes-support/libssh/libssh_0.10.6.bb   |   4 +
 .../python3-cbor2/CVE-2026-26209-pre1.patch   | 469 ++++++++++++++++++
 .../python/python3-cbor2/CVE-2026-26209.patch | 415 ++++++++++++++++
 .../python/python3-cbor2_5.6.4.bb             |   2 +
 15 files changed, 1194 insertions(+), 60 deletions(-)
 create mode 100644 meta-networking/recipes-support/strongswan/strongswan/CVE-2026-25075.patch
 create mode 100644 meta-oe/recipes-devtools/giflib/giflib/CVE-2026-23868.patch
 delete mode 100644 meta-oe/recipes-support/freerdp/freerdp/0001-Fix-const-qualifier-error.patch
 create mode 100644 meta-oe/recipes-support/libssh/libssh/CVE-2026-0964.patch
 create mode 100644 meta-oe/recipes-support/libssh/libssh/CVE-2026-0966-1.patch
 create mode 100644 meta-oe/recipes-support/libssh/libssh/CVE-2026-0966-2.patch
 create mode 100644 meta-oe/recipes-support/libssh/libssh/CVE-2026-0966-3.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-cbor2/CVE-2026-26209-pre1.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-cbor2/CVE-2026-26209.patch

-- 
2.53.0



             reply	other threads:[~2026-04-05 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 13:27 Anuj Mittal [this message]
2026-04-05 15:36 ` [oe] [PATCH 0/7] Scarthgap pull request Khem Raj

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.1775370794.git.anuj.mittal@oss.qualcomm.com \
    --to=anuj.mittal@oss.qualcomm.com \
    --cc=openembedded-devel@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