From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <randy.macleod@windriver.com>
Subject: [hardknott][PATCH 0/4] Fix CVEs of xserver-xorg
Date: Wed, 29 Dec 2021 09:30:47 +0800 [thread overview]
Message-ID: <20211229013051.36342-1-kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
Kai Kang (4):
xserver-xorg: fix CVE-2021-4008
xserver-xorg: fix CVE-2021-4009
xserver-xorg: fix CVE-2021-4010
xserver-xorg: fix CVE-2021-4011
.../xserver-xorg/CVE-2021-4008.patch | 59 +++++++++++++++++++
.../xserver-xorg/CVE-2021-4009.patch | 50 ++++++++++++++++
.../xserver-xorg/CVE-2021-4010.patch | 39 ++++++++++++
.../xserver-xorg/CVE-2021-4011.patch | 40 +++++++++++++
.../xorg-xserver/xserver-xorg_1.20.10.bb | 4 ++
5 files changed, 192 insertions(+)
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2021-4008.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2021-4009.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2021-4010.patch
create mode 100644 meta/recipes-graphics/xorg-xserver/xserver-xorg/CVE-2021-4011.patch
--
2.17.1
next reply other threads:[~2021-12-29 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 1:30 kai.kang [this message]
2021-12-29 1:30 ` [hardknott][PATCH 1/4] xserver-xorg: fix CVE-2021-4008 kai.kang
2021-12-29 1:30 ` [hardknott][PATCH 2/4] xserver-xorg: fix CVE-2021-4009 kai.kang
2021-12-29 1:30 ` [hardknott][PATCH 3/4] xserver-xorg: fix CVE-2021-4010 kai.kang
2021-12-29 1:30 ` [hardknott][PATCH 4/4] xserver-xorg: fix CVE-2021-4011 kai.kang
[not found] ` <16C515AB4535CCA0.27787@lists.openembedded.org>
2022-01-07 2:56 ` [OE-core] [hardknott][PATCH 1/4] xserver-xorg: fix CVE-2021-4008 Kai
2022-01-07 7:51 ` Mittal, Anuj
2022-01-07 7:56 ` Kai
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=20211229013051.36342-1-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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