From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Cetola, Stephano" <stephano.cetola@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v2 0/2] Fix bugs in HiiDatabase driver
Date: Fri, 8 Mar 2019 03:17:26 +0000 [thread overview]
Message-ID: <D827630B58408649ACB04F44C5100036258C39C7@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <20190308023514.103228-1-ray.ni@intel.com>
Hi all,
This is a very important fix for this issue. If no objection, I'd like the patch be part of this stable tag.
As to this patch series,
Reviewed-by: Jian J Wang <jian.j.wang@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ray Ni
> Sent: Friday, March 08, 2019 10:35 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH v2 0/2] Fix bugs in HiiDatabase driver
>
> v2: put the CVE number in patch title.
>
> Ray Ni (2):
> MdeModulePkg/HiiDatabase: Fix potential integer overflow
> (CVE-2018-12181)
> MdeModulePkg/HiiImage: Fix stack overflow when corrupted BMP is parsed
> (CVE-2018-12181)
>
> MdeModulePkg/Universal/HiiDatabaseDxe/Image.c | 130 ++++++++++++++----
> 1 file changed, 105 insertions(+), 25 deletions(-)
>
> --
> 2.20.1.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2019-03-08 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 2:35 [PATCH v2 0/2] Fix bugs in HiiDatabase driver Ray Ni
2019-03-08 2:35 ` [PATCH v2 1/2] MdeModulePkg/HiiDatabase: Fix potential integer overflow (CVE-2018-12181) Ray Ni
2019-03-08 2:44 ` Wu, Hao A
2019-03-08 2:35 ` [PATCH v2 2/2] MdeModulePkg/HiiImage: Fix stack overflow when corrupted BMP is parsed (CVE-2018-12181) Ray Ni
2019-03-08 3:17 ` Wang, Jian J [this message]
2019-03-08 6:41 ` [PATCH v2 0/2] Fix bugs in HiiDatabase driver Gao, Liming
2019-03-08 8:52 ` Laszlo Ersek
2019-03-08 12:50 ` Laszlo Ersek
2019-03-08 16:00 ` Gao, Liming
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=D827630B58408649ACB04F44C5100036258C39C7@SHSMSX107.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