From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] patch: fix CVE-2018-6951 and CVE-2018-1000156
Date: Wed, 11 Apr 2018 14:56:08 +0800 [thread overview]
Message-ID: <cover.1523429249.git.jackie.huang@windriver.com> (raw)
From: Jackie Huang <jackie.huang@windriver.com>
These are also needed for previous releases, so I think they should be
backported to the branch for 2.5 and 2.4 as well.
--
The following changes since commit 29f65bda6d2c9fea4adb125c4857ee64f9312b9f:
nativesdk-glibc: Split glibc and libcrypt to use libxcrypt instead (2018-04-07 22:34:45 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib.git jhuang0/d_patch_CVEs_180411_0
http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/d_patch_CVEs_180411_0
Jackie Huang (2):
patch: fix CVE-2018-6951
patch: fix CVE-2018-1000156
...02-Fix-segfault-with-mangled-rename-patch.patch | 35 ++++
...-files-to-be-missing-for-ed-style-patches.patch | 38 ++++
...ry-command-execution-in-ed-style-patches-.patch | 215 +++++++++++++++++++++
meta/recipes-devtools/patch/patch_2.7.6.bb | 6 +-
4 files changed, 293 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools/patch/patch/0002-Fix-segfault-with-mangled-rename-patch.patch
create mode 100644 meta/recipes-devtools/patch/patch/0003-Allow-input-files-to-be-missing-for-ed-style-patches.patch
create mode 100644 meta/recipes-devtools/patch/patch/0004-Fix-arbitrary-command-execution-in-ed-style-patches-.patch
--
2.11.0
next reply other threads:[~2018-04-11 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 6:56 jackie.huang [this message]
2018-04-11 6:56 ` [PATCH 1/2] patch: fix CVE-2018-6951 jackie.huang
2018-04-11 6:56 ` [PATCH 2/2] patch: fix CVE-2018-1000156 jackie.huang
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.1523429249.git.jackie.huang@windriver.com \
--to=jackie.huang@windriver.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