From: "Ni, Ray" <ray.ni@intel.com>
To: "Gao, Zhichao" <zhichao.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v3] UefiCpuPkg/MpInitLib: MicrocodeDetect: Ensure checked range is valid
Date: Wed, 26 Jun 2019 05:58:38 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C1F0EC8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190626053158.6060-1-zhichao.gao@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: Gao, Zhichao <zhichao.gao@intel.com>
> Sent: Wednesday, June 26, 2019 1:32 PM
> To: devel@edk2.groups.io
> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; Laszlo
> Ersek <lersek@redhat.com>; Gao, Liming <liming.gao@intel.com>
> Subject: [PATCH v3] UefiCpuPkg/MpInitLib: MicrocodeDetect: Ensure
> checked range is valid
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1934
>
> 0x0 MicrocodeBegin MicrocodeEntry MicrocodeEnd 0xffffffff
> |--------------|---------------|---------------|---------------|
> valid TotalSize TotalSize is only valid between 0 and
> (MicrocodeEnd - MicrocodeEntry).
> So add '(UINTN)MicrocodeEntryPoint > (MAX_ADDRESS - TotalSize)' before
> '((UINTN)MicrocodeEntryPoint + TotalSize) > MicrocodeEnd' to make sure
> ((UINTN)MicrocodeEntryPoint + TotalSize) wouldn't overflow.
>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
> ---
> UefiCpuPkg/Library/MpInitLib/Microcode.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/UefiCpuPkg/Library/MpInitLib/Microcode.c
> b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> index 4763dcfebe..c30df58e5a 100644
> --- a/UefiCpuPkg/Library/MpInitLib/Microcode.c
> +++ b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> @@ -1,7 +1,7 @@
> /** @file
> Implementation of loading microcode on processors.
>
> - Copyright (c) 2015 - 2018, Intel Corporation. All rights reserved.<BR>
> + Copyright (c) 2015 - 2019, Intel Corporation. All rights
> + reserved.<BR>
> SPDX-License-Identifier: BSD-2-Clause-Patent
>
> **/
> @@ -167,9 +167,15 @@ MicrocodeDetect (
> }
>
> ///
> - /// Check overflow and whether TotalSize is aligned with 4 bytes.
> + /// 0x0 MicrocodeBegin MicrocodeEntry MicrocodeEnd 0xffffffff
> + /// |--------------|---------------|---------------|---------------|
> + /// valid TotalSize
> + /// TotalSize is only valid between 0 and (MicrocodeEnd -
> MicrocodeEntry).
> + /// And it should be aligned with 4 bytes.
> + /// If the TotalSize is invalid skip 1KB the check next entry.
> ///
> - if ( ((UINTN)MicrocodeEntryPoint + TotalSize) > MicrocodeEnd ||
> + if ( (UINTN)MicrocodeEntryPoint > (MAX_ADDRESS - TotalSize) ||
> + ((UINTN)MicrocodeEntryPoint + TotalSize) > MicrocodeEnd ||
> (TotalSize & 0x3) != 0
> ) {
> MicrocodeEntryPoint = (CPU_MICROCODE_HEADER *) (((UINTN)
> MicrocodeEntryPoint) + SIZE_1KB);
> --
> 2.21.0.windows.1
prev parent reply other threads:[~2019-06-26 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 5:31 [PATCH v3] UefiCpuPkg/MpInitLib: MicrocodeDetect: Ensure checked range is valid Gao, Zhichao
2019-06-26 5:58 ` Ni, Ray [this message]
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=734D49CCEBEEF84792F5B80ED585239D5C1F0EC8@SHSMSX104.ccr.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