From: Hao Wu <hao.a.wu@intel.com>
To: edk2-devel@lists.01.org
Cc: Hao Wu <hao.a.wu@intel.com>, Jiewen Yao <jiewen.yao@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Eric Dong <eric.dong@intel.com>
Subject: [PATCH v1 0/1][UDK branches][CVE-2017-5715] Stuff RSB before RSM
Date: Fri, 16 Nov 2018 09:37:09 +0800 [thread overview]
Message-ID: <20181116013710.33800-1-hao.a.wu@intel.com> (raw)
The series aims to mitigate the Branch Target Injection (CVE-2017-5715)
issues for 'RSM' instructions. Moreover, this series focuses on the UDK
branches where .NASM file is not added for a module.
Patch 1/1 will be applied on the below UDK branches:
UDK2015
A more detailed explanation of the purpose of commit is under the
'Branch target injection mitigation' section of the below link:
https://software.intel.com/security-software-guidance/insights/host-firmware-speculative-execution-side-channel-mitigation
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Hao Wu (1):
UefiCpuPkg: [CVE-2017-5715] Stuff RSB before RSM
UefiCpuPkg/Include/StuffRsbAsm.inc | 60 ++++++++++++++++++++
UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmiEntry.asm | 5 +-
UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.asm | 5 +-
UefiCpuPkg/PiSmmCpuDxeSmm/X64/SmiEntry.asm | 5 +-
UefiCpuPkg/PiSmmCpuDxeSmm/X64/SmmInit.asm | 5 +-
5 files changed, 76 insertions(+), 4 deletions(-)
create mode 100644 UefiCpuPkg/Include/StuffRsbAsm.inc
--
2.12.0.windows.1
next reply other threads:[~2018-11-16 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 1:37 Hao Wu [this message]
2018-11-16 1:37 ` [PATCH v1 1/1] UefiCpuPkg: [CVE-2017-5715] Stuff RSB before RSM Hao Wu
2018-11-19 2:00 ` Dong, Eric
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-list 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=20181116013710.33800-1-hao.a.wu@intel.com \
--to=devel@edk2.groups.io \
/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