From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/16] Pull request (cover letter only)
Date: Fri, 27 Jan 2023 16:22:22 -1000 [thread overview]
Message-ID: <cover.1674872492.git.steve@sakoman.com> (raw)
The following changes since commit db81e3c7e7f1d4d9eba52ac35ac97627d0240b63:
build-appliance-image: Update to dunfell head revision (2023-01-13 18:11:40 +0000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Alexander Kanavin (2):
linux-firmware: upgrade 20221109 -> 20221214
selftest/virgl: use pkg-config from the host
Benoît Mauduit (1):
lib/oe/reproducible: Use git log without gpg signature
Bhabu Bindu (1):
ffmpeg: Fix CVE-2022-3109
Hitendra Prajapati (2):
QEMU: CVE-2022-4144 QXL: qxl_phys2virt unsafe address translation can
lead to out-of-bounds read
xserver-xorg: Fix Multiple CVEs
Jan Kircher (1):
toolchain-scripts: compatibility with unbound variable protection
Jermain Horsman (1):
cve-check: write the cve manifest to IMGDEPLOYDIR
Marta Rybczynska (1):
cve-update-db-native: avoid incomplete updates
Niko Mauno (1):
systemd: Consider PACKAGECONFIG in RRECOMMENDS
Quentin Schulz (1):
cairo: fix CVE patches assigned wrong CVE number
Randy MacLeod (1):
vim: upgrade 9.0.0947 -> 9.0.1211
Ross Burton (2):
cve-update-db-native: add more logging when fetching
cve-update-db-native: show IP on failure
Steve Sakoman (1):
python3: fix packaging of Windows distutils installer stubs
jan (1):
cve-update-db-native: Allow to overrule the URL in a bbappend.
meta/classes/cve-check.bbclass | 6 +-
meta/classes/toolchain-scripts.bbclass | 2 +-
meta/lib/oe/reproducible.py | 3 +-
meta/lib/oeqa/selftest/cases/runtime_test.py | 2 +-
.../recipes-core/meta/cve-update-db-native.bb | 97 ++++++++++++-----
meta/recipes-core/systemd/systemd_244.5.bb | 4 +-
.../python/python3/python3-manifest.json | 4 +-
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2022-4144.patch | 103 ++++++++++++++++++
.../cairo/cairo/CVE-2019-6461.patch | 46 +++-----
.../cairo/cairo/CVE-2019-6462.patch | 46 +++++---
.../xserver-xorg/CVE-2022-4283.patch | 39 +++++++
.../xserver-xorg/CVE-2022-46340.patch | 55 ++++++++++
.../xserver-xorg/CVE-2022-46341.patch | 86 +++++++++++++++
.../xserver-xorg/CVE-2022-46342.patch | 78 +++++++++++++
.../xserver-xorg/CVE-2022-46343.patch | 51 +++++++++
.../xserver-xorg/CVE-2022-46344.patch | 75 +++++++++++++
.../xorg-xserver/xserver-xorg_1.20.14.bb | 8 +-
...20221109.bb => linux-firmware_20221214.bb} | 4 +-
.../ffmpeg/ffmpeg/CVE-2022-3109.patch | 41 +++++++
.../recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb | 1 +
meta/recipes-support/vim/vim.inc | 4 +-
22 files changed, 670 insertions(+), 86 deletions(-)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2022-4144.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-4283.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-46340.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-46341.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-46342.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-46343.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2022-46344.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20221109.bb => linux-firmware_20221214.bb} (99%)
create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2022-3109.patch
--
2.25.1
next reply other threads:[~2023-01-28 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 2:22 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 14:13 [OE-core][dunfell 00/16] Pull request (cover letter only) Steve Sakoman
2022-10-26 23:03 Steve Sakoman
2021-08-17 2:53 Steve Sakoman
2020-12-03 23:46 Steve Sakoman
2020-11-17 23:44 Steve Sakoman
2020-10-30 3:48 Steve Sakoman
2020-05-28 3:04 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.1674872492.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