From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 0/6] Patch review
Date: Mon, 13 May 2024 05:18:06 -0700 [thread overview]
Message-ID: <cover.1715602539.git.steve@sakoman.com> (raw)
Please review this set of changes for kirkstone and have comments back by
end of day Wednesday, May 17
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6895
The following changes since commit 24fd9b6756728a0337100f53a1c6e92aba092f9d:
ppp: Add RSA-MD in LICENSE (2024-05-08 05:19:26 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
Archana Polampalli (2):
xserver-xorg: fix CVE-2024-31082
xserver-xorg: fix CVE-2024-31083
Bhabu Bindu (1):
libpciaccess: Remove duplicated license entry
Peter Marko (1):
glibc: Update to latest on stable 2.35 branch
Vijay Anusuri (2):
bluez5: Fix CVE-2023-27349 CVE-2023-50229 & CVE-2023-50230
gstreamer1.0-plugins-bad: fix CVE-2023-50186
meta/recipes-connectivity/bluez5/bluez5.inc | 2 +
.../bluez5/bluez5/CVE-2023-27349.patch | 48 +++++++
.../CVE-2023-50229_CVE-2023-50230.patch | 67 ++++++++++
meta/recipes-core/glibc/glibc-version.inc | 2 +-
...y-the-header-between-arm-and-aarch64.patch | 64 +++++-----
meta/recipes-core/glibc/glibc_2.35.bb | 5 +-
.../xorg-lib/libpciaccess_0.16.bb | 2 +-
.../xserver-xorg/CVE-2024-31082.patch | 52 ++++++++
.../xserver-xorg/CVE-2024-31083-0001.patch | 117 ++++++++++++++++++
.../xserver-xorg/CVE-2024-31083-0002.patch | 76 ++++++++++++
.../xorg-xserver/xserver-xorg_21.1.8.bb | 3 +
.../CVE-2023-50186.patch | 70 +++++++++++
.../gstreamer1.0-plugins-bad_1.20.7.bb | 1 +
13 files changed, 478 insertions(+), 31 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2023-27349.patch
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2023-50229_CVE-2023-50230.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2024-31082.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2024-31083-0001.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2024-31083-0002.patch
create mode 100644 meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/CVE-2023-50186.patch
--
2.34.1
next reply other threads:[~2024-05-13 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 12:18 Steve Sakoman [this message]
2024-05-13 12:18 ` [OE-core][kirkstone 1/6] xserver-xorg: fix CVE-2024-31082 Steve Sakoman
2024-05-13 12:18 ` [OE-core][kirkstone 2/6] xserver-xorg: fix CVE-2024-31083 Steve Sakoman
2024-05-13 12:18 ` [OE-core][kirkstone 3/6] bluez5: Fix CVE-2023-27349 CVE-2023-50229 & CVE-2023-50230 Steve Sakoman
2024-05-13 12:18 ` [OE-core][kirkstone 4/6] gstreamer1.0-plugins-bad: fix CVE-2023-50186 Steve Sakoman
2024-05-13 12:18 ` [OE-core][kirkstone 5/6] glibc: Update to latest on stable 2.35 branch Steve Sakoman
2024-05-13 12:18 ` [OE-core][kirkstone 6/6] libpciaccess: Remove duplicated license entry Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-01-21 18:57 [OE-core][kirkstone 0/6] Patch review Steve Sakoman
2024-01-08 16:14 Steve Sakoman
2023-10-21 15:28 Steve Sakoman
2023-04-05 2:29 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.1715602539.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).