From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Laszlo Ersek <lersek@redhat.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Zeng, Star" <star.zeng@intel.com>,
"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH v1 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers
Date: Thu, 20 Sep 2018 13:59:16 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8ADAA67@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <20180920064103.14600-1-hao.a.wu@intel.com>
Hao Wu,
I see that implementations of this API are only
provided for IA32 and X64. Should this be an IA32/X64
specific API in BaseLib? Also, since the API is providing
a C callable function to execute a specific IA32/X64
instruction, should the API be prefixed with Asm to
match the convention of other APIs in BaseLib?
Thanks,
Mike
> -----Original Message-----
> From: Wu, Hao A
> Sent: Wednesday, September 19, 2018 11:41 PM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Ard Biesheuvel
> <ard.biesheuvel@linaro.org>; Laszlo Ersek
> <lersek@redhat.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Gao, Liming
> <liming.gao@intel.com>; Zeng, Star
> <star.zeng@intel.com>; Dong, Eric <eric.dong@intel.com>
> Subject: [PATCH v1 0/5] [CVE-2017-5753] Bounds Check
> Bypass issue in SMI handlers
>
> The series aims to mitigate the Bounds Check Bypass
> (CVE-2017-5753) issues
> within SMI handlers.
>
> A more detailed explanation of the purpose of the
> series is under the
> 'Bounds check bypass mitigation' section of the below
> link:
> https://software.intel.com/security-software-
> guidance/insights/host-firmware-speculative-execution-
> side-channel-mitigation
>
> And the document at:
> https://software.intel.com/security-software-
> guidance/api-app/sites/default/files/337879-analyzing-
> potential-bounds-Check-bypass-vulnerabilities.pdf
>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
>
> Hao Wu (5):
> MdePkg/BaseLib: Add new LoadFence API
> MdeModulePkg/FaultTolerantWrite:[CVE-2017-5753]Fix
> bounds check bypass
> MdeModulePkg/SmmLockBox: [CVE-2017-5753] Fix bounds
> check bypass
> MdeModulePkg/Variable: [CVE-2017-5753] Fix bounds
> check bypass
> UefiCpuPkg/PiSmmCpuDxeSmm: [CVE-2017-5753] Fix bounds
> check bypass
>
>
> MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultToler
> antWriteSmm.c | 2 ++
>
> MdeModulePkg/Universal/FaultTolerantWriteDxe/FaultToler
> antWriteSmm.inf | 1 +
> MdeModulePkg/Universal/LockBox/SmmLockBox/SmmLockBox.c
> | 2 ++
> MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> | 1 +
>
> MdeModulePkg/Universal/Variable/RuntimeDxe/VariableSmm.
> c | 3 ++
> MdePkg/Include/Library/BaseLib.h
> | 12 +++++++
> MdePkg/Library/BaseLib/Arm/LoadFence.c
> | 26 ++++++++++++++
> MdePkg/Library/BaseLib/BaseLib.inf
> | 4 +++
> MdePkg/Library/BaseLib/Ebc/CpuBreakpoint.c
> | 15 +++++++-
> MdePkg/Library/BaseLib/Ia32/LoadFence.nasm
> | 37 +++++++++++++++++++
> MdePkg/Library/BaseLib/X64/LoadFence.nasm
> | 38 ++++++++++++++++++++
> UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.c
> | 1 +
> 12 files changed, 141 insertions(+), 1 deletion(-)
> create mode 100644
> MdePkg/Library/BaseLib/Arm/LoadFence.c
> create mode 100644
> MdePkg/Library/BaseLib/Ia32/LoadFence.nasm
> create mode 100644
> MdePkg/Library/BaseLib/X64/LoadFence.nasm
>
> --
> 2.12.0.windows.1
next prev parent reply other threads:[~2018-09-20 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 6:40 [PATCH v1 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers Hao Wu
2018-09-20 6:40 ` [PATCH v1 1/5] MdePkg/BaseLib: Add new LoadFence API Hao Wu
2018-09-20 13:13 ` Laszlo Ersek
2018-09-21 2:14 ` Wu, Hao A
2018-09-21 2:21 ` Yao, Jiewen
2018-09-21 2:38 ` Wu, Hao A
2018-09-20 6:41 ` [PATCH v1 2/5] MdeModulePkg/FaultTolerantWrite:[CVE-2017-5753]Fix bounds check bypass Hao Wu
2018-09-20 6:41 ` [PATCH v1 3/5] MdeModulePkg/SmmLockBox: [CVE-2017-5753] Fix " Hao Wu
2018-09-20 6:41 ` [PATCH v1 4/5] MdeModulePkg/Variable: " Hao Wu
2018-09-20 6:41 ` [PATCH v1 5/5] UefiCpuPkg/PiSmmCpuDxeSmm: " Hao Wu
2018-09-20 13:22 ` [PATCH v1 0/5] [CVE-2017-5753] Bounds Check Bypass issue in SMI handlers Laszlo Ersek
2018-09-20 13:59 ` Kinney, Michael D [this message]
2018-09-21 2:14 ` Wu, Hao A
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=E92EE9817A31E24EB0585FDF735412F5B8ADAA67@ORSMSX113.amr.corp.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