From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/5] Patch review
Date: Tue, 19 Dec 2023 03:48:18 -1000 [thread overview]
Message-ID: <cover.1702993573.git.steve@sakoman.com> (raw)
Please review this set of changes for dunfell and have comments back by
end of day Thursday, December 21
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6348
The following changes since commit 55157aa2f8b157b1cc63e1134d9eba6db0cf16da:
build-appliance-image: Update to dunfell head revision (2023-12-11 05:13:51 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Bhabu Bindu (1):
glibc: Fix CVE-2023-4813
Lee Chee Yang (2):
perl: fix CVE-2023-31484/47038/47100
binutils: Fix CVE-2023-25584
Vijay Anusuri (1):
libxml2: Backport fix for CVE-2021-3516
Vivek Kumbhar (1):
libsndfile: fix CVE-2021-4156 heap out-of-bounds read in src/flac.c in
flac_buffer_copy
.../glibc/glibc/CVE-2023-4813.patch | 986 ++++++++++++++++++
meta/recipes-core/glibc/glibc_2.31.bb | 1 +
.../libxml/libxml2/CVE-2021-3516.patch | 35 +
meta/recipes-core/libxml/libxml2_2.9.10.bb | 1 +
.../binutils/binutils-2.34.inc | 1 +
.../binutils/binutils/CVE-2023-25584.patch | 530 ++++++++++
.../perl/files/CVE-2023-31484.patch | 27 +
.../perl/files/CVE-2023-47038.patch | 121 +++
meta/recipes-devtools/perl/perl_5.30.1.bb | 2 +
.../libsndfile1/CVE-2021-4156.patch | 30 +
.../libsndfile/libsndfile1_1.0.28.bb | 1 +
11 files changed, 1735 insertions(+)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2023-4813.patch
create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2021-3516.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2023-25584.patch
create mode 100644 meta/recipes-devtools/perl/files/CVE-2023-31484.patch
create mode 100644 meta/recipes-devtools/perl/files/CVE-2023-47038.patch
create mode 100644 meta/recipes-multimedia/libsndfile/libsndfile1/CVE-2021-4156.patch
--
2.34.1
next reply other threads:[~2023-12-19 13:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 13:48 Steve Sakoman [this message]
2023-12-19 13:48 ` [OE-core][dunfell 1/5] glibc: Fix CVE-2023-4813 Steve Sakoman
2023-12-19 13:48 ` [OE-core][dunfell 2/5] perl: fix CVE-2023-31484/47038/47100 Steve Sakoman
2023-12-19 13:48 ` [OE-core][dunfell 3/5] binutils: Fix CVE-2023-25584 Steve Sakoman
2023-12-19 13:48 ` [OE-core][dunfell 4/5] libsndfile: fix CVE-2021-4156 heap out-of-bounds read in src/flac.c in flac_buffer_copy Steve Sakoman
2023-12-19 13:48 ` [OE-core][dunfell 5/5] libxml2: Backport fix for CVE-2021-3516 Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 13:10 [OE-core][dunfell 0/5] Patch review Steve Sakoman
2024-01-05 14:03 Steve Sakoman
2023-09-04 14:22 Steve Sakoman
2023-06-14 14:04 Steve Sakoman
2022-09-22 21:47 Steve Sakoman
2021-09-07 14:44 Steve Sakoman
2021-09-03 14:10 Steve Sakoman
2020-11-21 0:13 Steve Sakoman
2020-06-03 15:33 Steve Sakoman
2020-06-03 17:33 ` akuster
2020-06-03 17:36 ` Denys Dmytriyenko
2020-06-03 17:45 ` akuster
2020-06-03 23:33 ` Martin Jansa
2020-06-04 0:11 ` Joshua Watt
2020-06-04 0:38 ` Martin Jansa
2020-06-03 18:17 ` akuster
2020-06-03 18:18 ` Denys Dmytriyenko
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.1702993573.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