From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/10] Pull request (cover letter only)
Date: Tue, 29 Mar 2022 12:10:39 -1000 [thread overview]
Message-ID: <cover.1648591772.git.steve@sakoman.com> (raw)
The following changes since commit 71015408c60ddf2e9af00cc8574815971e1b689d:
oeqa/selftest/tinfoil: Improve tinfoil event test debugging (2022-03-21 04:17:02 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Davide Gardenal (3):
qemu: backport patch fix for CVE-2020-13791
apt: backport patch fix for CVE-2020-3810
ghostscript: backport patch fix for CVE-2021-3781
Minjae Kim (2):
gnu-config: update SRC_URI
virglrenderer: update SRC_URI
Ralph Siemsen (1):
libxml2: fix CVE-2022-23308 regression
Richard Purdie (1):
oeqa/selftest/tinfoil: Fix intermittent event loss issue in test
Ross Burton (1):
python3: ignore CVE-2022-26488
Steve Sakoman (2):
libsolv: fix CVE: CVE-2021-44568-71 and CVE-2021-44573-77
ghostscript: fix CVE-2020-15900 and CVE-2021-45949 for -native
meta/lib/oeqa/selftest/cases/tinfoil.py | 2 +-
.../CVE-2022-23308-fix-regression.patch | 98 ++++++++
meta/recipes-core/libxml/libxml2_2.9.10.bb | 1 +
meta/recipes-devtools/apt/apt.inc | 1 +
.../apt/apt/CVE-2020-3810.patch | 174 +++++++++++++
.../gnu-config/gnu-config_git.bb | 2 +-
.../recipes-devtools/python/python3_3.8.13.bb | 2 +-
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2020-13791.patch | 44 ++++
.../ghostscript/CVE-2021-3781_1.patch | 121 +++++++++
.../ghostscript/CVE-2021-3781_2.patch | 37 +++
.../ghostscript/CVE-2021-3781_3.patch | 238 ++++++++++++++++++
.../ghostscript/ghostscript_9.52.bb | 9 +-
.../libsolv/files/CVE-2021-3200.patch | 10 +
.../virglrenderer/virglrenderer_0.8.2.bb | 2 +-
15 files changed, 735 insertions(+), 7 deletions(-)
create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-23308-fix-regression.patch
create mode 100644 meta/recipes-devtools/apt/apt/CVE-2020-3810.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2020-13791.patch
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2021-3781_1.patch
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2021-3781_2.patch
create mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2021-3781_3.patch
--
2.25.1
next reply other threads:[~2022-03-29 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 22:10 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-14 16:57 [OE-core][dunfell 00/10] Pull request (cover letter only) Steve Sakoman
2021-05-04 14:09 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.1648591772.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