From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/12] Pull request (cover letter only)
Date: Thu, 10 Feb 2022 16:04:51 +0800 [thread overview]
Message-ID: <cover.1644480182.git.anuj.mittal@intel.com> (raw)
The following changes since commit d54d7e7b43da621be8e6fcca34feb7b3d49b8160:
lighttpd: backport a fix for CVE-2022-22707 (2022-01-26 11:40:00 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Alexander Kanavin (1):
libusb1: correct SRC_URI
Bruce Ashfield (2):
linux-yocto/5.10: update to v5.10.92
linux-yocto/5.10: update to v5.10.93
Peter Kjellerstedt (1):
sstate: A third fix for for touching files inside pseudo
Ross Burton (1):
yocto-check-layer: add debug output for the layers that were found
Rudolf J Streif (1):
linux-firmware: Add CLM blob to linux-firmware-bcm4373 package
Sakib Sajal (4):
qemu: fix CVE-2021-3713
qemu: fix CVE-2021-3748
qemu: fix CVE-2021-3930
qemu: fix CVE-2021-20196
Steve Sakoman (2):
expat: fix CVE-2022-23852
expat: add missing Upstream-status, CVE tag and sign-off to
CVE-2021-46143.patch
meta/classes/sstate.bbclass | 14 +-
.../expat/expat/CVE-2021-46143.patch | 6 +
.../expat/expat/CVE-2022-23852.patch | 33 +++++
meta/recipes-core/expat/expat_2.2.10.bb | 1 +
meta/recipes-devtools/qemu/qemu.inc | 5 +
.../qemu/qemu/CVE-2021-20196_1.patch | 54 ++++++++
.../qemu/qemu/CVE-2021-20196_2.patch | 67 +++++++++
.../qemu/qemu/CVE-2021-3713.patch | 68 ++++++++++
.../qemu/qemu/CVE-2021-3748.patch | 127 ++++++++++++++++++
.../qemu/qemu/CVE-2021-3930.patch | 53 ++++++++
.../linux-firmware/linux-firmware_20211216.bb | 1 +
.../linux/linux-yocto-rt_5.10.bb | 6 +-
.../linux/linux-yocto-tiny_5.10.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++--
meta/recipes-support/libusb/libusb1_1.0.24.bb | 6 +-
scripts/yocto-check-layer | 13 ++
16 files changed, 460 insertions(+), 26 deletions(-)
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-23852.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-20196_1.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-20196_2.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3713.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3748.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3930.patch
--
2.34.1
reply other threads:[~2022-02-10 8:05 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.1644480182.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.