From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/23] Pull request (cover letter only)
Date: Thu, 9 Mar 2023 16:48:55 -1000 [thread overview]
Message-ID: <cover.1678416279.git.steve@sakoman.com> (raw)
The following changes since commit a3f31997c633e8476bad68c81fac0dcd0750c7d4:
busybox: rm temporary files if do_compile was interrupted (2023-02-20 05:51:44 -1000)
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 (6):
vim: update 9.0.1211 -> 9.0.1293 to resolve open CVEs
linux-firmware: upgrade 20221214 -> 20230117
linux-firmware: upgrade 20230117 -> 20230210
wireless-regdb: upgrade 2022.08.12 -> 2023.02.13
apr: update 1.7.0 -> 1.7.2
apr-util: update 1.6.1 -> 1.6.3
Chee Yang Lee (1):
tiff: fix multiple CVEs
Dmitry Baryshkov (2):
linux-firmware: properly set license for all Qualcomm firmware
linux-firmware: add yamato fw files to qcom-adreno-a2xx package
Hitendra Prajapati (1):
curl: fix CVE-2022-43552 Use-after-free triggered by an HTTP proxy
deny response
Hugo SIMELIERE (2):
bluez5: Exclude CVE-2022-39177 from cve-check
openssl: upgrade 1.1.1s to 1.1.1t
Khem Raj (2):
apr: Use correct strerror_r implementation based on libc type
apr: Cache configure tests which use AC_TRY_RUN
Mauro Queiros (1):
image.bbclass: print all QA functions exceptions
Peter Kjellerstedt (1):
devshell: Do not add scripts/git-intercept to PATH
Richard Purdie (2):
apr: Fix to work with autoconf 2.70
apr-util: Fix CFLAGS used in build
Rodolfo Quesada Zumbado (1):
tar: CVE-2022-48303
Shubham Kulkarni (1):
glibc: Security fix for CVE-2023-0687
Ulrich Ölmann (1):
kernel-yocto: fix kernel-meta data detection
Vijay Anusuri (1):
git: Security fix for CVE-2022-41903
Virendra Thakur (1):
gcc: Fix inconsistent noexcept specifier for valarray in libstdc++
meta/classes/devshell.bbclass | 2 -
meta/classes/image.bbclass | 2 +-
meta/classes/kernel-yocto.bbclass | 2 +-
meta/lib/oeqa/selftest/cases/reproducible.py | 1 -
.../bluez5/bluez5_5.55.bb | 7 +
.../{openssl_1.1.1s.bb => openssl_1.1.1t.bb} | 2 +-
.../glibc/glibc/CVE-2023-0687.patch | 82 +++
meta/recipes-core/glibc/glibc_2.31.bb | 1 +
meta/recipes-devtools/gcc/gcc-9.5.inc | 1 +
...nsistent-noexcept-specific-for-valar.patch | 44 ++
.../git/files/CVE-2022-41903-01.patch | 39 ++
.../git/files/CVE-2022-41903-02.patch | 187 +++++
.../git/files/CVE-2022-41903-03.patch | 146 ++++
.../git/files/CVE-2022-41903-04.patch | 150 ++++
.../git/files/CVE-2022-41903-05.patch | 98 +++
.../git/files/CVE-2022-41903-06.patch | 90 +++
.../git/files/CVE-2022-41903-07.patch | 123 ++++
.../git/files/CVE-2022-41903-08.patch | 67 ++
.../git/files/CVE-2022-41903-09.patch | 162 +++++
.../git/files/CVE-2022-41903-10.patch | 99 +++
.../git/files/CVE-2022-41903-11.patch | 90 +++
.../git/files/CVE-2022-41903-12.patch | 124 ++++
meta/recipes-devtools/git/git.inc | 12 +
.../tar/tar/CVE-2022-48303.patch | 43 ++
meta/recipes-extended/tar/tar_1.32.bb | 1 +
...20221214.bb => linux-firmware_20230210.bb} | 42 +-
....08.12.bb => wireless-regdb_2023.02.13.bb} | 2 +-
.../libtiff/files/CVE-2022-3570_3598.patch | 659 ++++++++++++++++++
.../files/CVE-2022-3597_3626_3627.patch | 123 ++++
.../libtiff/files/CVE-2022-3599.patch | 277 ++++++++
.../libtiff/files/CVE-2022-3970.patch | 45 ++
.../libtiff/files/CVE-2022-48281.patch | 26 +
.../CVE-2023-0795_0796_0797_0798_0799.patch | 157 +++++
.../CVE-2023-0800_0801_0802_0803_0804.patch | 135 ++++
meta/recipes-multimedia/libtiff/tiff_4.1.0.bb | 7 +
.../0001-Fix-error-handling-in-gdbm.patch | 135 ----
.../{apr-util_1.6.1.bb => apr-util_1.6.3.bb} | 8 +-
...ion-to-disable-timed-dependant-tests.patch | 20 +-
...-runtime-test-for-mmap-that-can-map-.patch | 58 ++
...ir-path-references-from-installed-ap.patch | 25 +-
...configure.in-support-cross-compiling.patch | 63 --
...ze-doesn-t-match-in-glibc-when-cross.patch | 76 --
.../apr/apr/CVE-2021-35940.patch | 58 --
.../apr/apr/libtoolize_check.patch | 21 +-
.../apr/{apr_1.7.0.bb => apr_1.7.2.bb} | 24 +-
.../curl/curl/CVE-2022-43552.patch | 82 +++
meta/recipes-support/curl/curl_7.69.1.bb | 1 +
meta/recipes-support/vim/vim.inc | 4 +-
48 files changed, 3238 insertions(+), 385 deletions(-)
rename meta/recipes-connectivity/openssl/{openssl_1.1.1s.bb => openssl_1.1.1t.bb} (98%)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2023-0687.patch
create mode 100644 meta/recipes-devtools/gcc/gcc-9.5/0002-libstdc-Fix-inconsistent-noexcept-specific-for-valar.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-01.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-02.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-03.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-04.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-05.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-06.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-07.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-08.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-09.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-10.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-11.patch
create mode 100644 meta/recipes-devtools/git/files/CVE-2022-41903-12.patch
create mode 100644 meta/recipes-extended/tar/tar/CVE-2022-48303.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20221214.bb => linux-firmware_20230210.bb} (96%)
rename meta/recipes-kernel/wireless-regdb/{wireless-regdb_2022.08.12.bb => wireless-regdb_2023.02.13.bb} (94%)
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-3570_3598.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-3597_3626_3627.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-3599.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-3970.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2022-48281.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2023-0795_0796_0797_0798_0799.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2023-0800_0801_0802_0803_0804.patch
delete mode 100644 meta/recipes-support/apr/apr-util/0001-Fix-error-handling-in-gdbm.patch
rename meta/recipes-support/apr/{apr-util_1.6.1.bb => apr-util_1.6.3.bb} (92%)
create mode 100644 meta/recipes-support/apr/apr/0001-configure-Remove-runtime-test-for-mmap-that-can-map-.patch
delete mode 100644 meta/recipes-support/apr/apr/0003-Makefile.in-configure.in-support-cross-compiling.patch
delete mode 100644 meta/recipes-support/apr/apr/0006-apr-fix-off_t-size-doesn-t-match-in-glibc-when-cross.patch
delete mode 100644 meta/recipes-support/apr/apr/CVE-2021-35940.patch
rename meta/recipes-support/apr/{apr_1.7.0.bb => apr_1.7.2.bb} (80%)
create mode 100644 meta/recipes-support/curl/curl/CVE-2022-43552.patch
--
2.34.1
next reply other threads:[~2023-03-10 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 2:48 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 3:28 [OE-core][dunfell 00/23] Pull request (cover letter only) Steve Sakoman
2020-07-22 0:52 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.1678416279.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 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.