From: Laszlo Ersek <lersek@redhat.com>
To: Hao Wu <hao.a.wu@intel.com>, edk2-devel@lists.01.org
Cc: Star Zeng <star.zeng@intel.com>
Subject: Re: [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk
Date: Tue, 26 Feb 2019 12:45:24 +0100 [thread overview]
Message-ID: <a41faa3e-170b-00d6-cb19-1e08862a6240@redhat.com> (raw)
In-Reply-To: <20190226074557.11048-1-hao.a.wu@intel.com>
On 02/26/19 08:45, Hao Wu wrote:
> V2 changes:
>
> Correct CC list information.
>
>
> V1 history:
>
> The series will resolve a buffer cross boundary access issue during the
> use of RAM disks. It is the mitigation for issue CVE-2018-12180.
>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
>
> Hao Wu (2):
> MdeModulePkg/PartitionDxe: Ensure blocksize can hold MBR (CVE FIX)
> MdeModulePkg/RamDiskDxe: Ramdisk size be multiple of BlkSize (CVE FIX)
>
> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskImpl.h | 6 +++---
> MdeModulePkg/Universal/Disk/PartitionDxe/Gpt.c | 9 ++++++++-
> MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c | 9 ++++++++-
> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskBlockIo.c | 20 ++++++++++++++------
> MdeModulePkg/Universal/Disk/RamDiskDxe/RamDiskProtocol.c | 5 +++--
> 5 files changed, 36 insertions(+), 13 deletions(-)
>
Please put the exact CVE numbers in the subject lines.
Thanks
Laszlo
next prev parent reply other threads:[~2019-02-26 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 7:45 [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk Hao Wu
2019-02-26 7:45 ` [PATCH v2 1/2] MdeModulePkg/PartitionDxe: Ensure blocksize can hold MBR (CVE FIX) Hao Wu
2019-02-26 7:45 ` [PATCH v2 2/2] MdeModulePkg/RamDiskDxe: Ramdisk size be multiple of BlkSize " Hao Wu
2019-02-26 11:45 ` Laszlo Ersek [this message]
2019-02-26 12:57 ` [PATCH v2 0/2] MdeModulePkg: Resolve buffer cross boundary access in Ramdisk Wu, Hao A
2019-02-27 6:56 ` Wu, Hao A
2019-02-27 8:58 ` Laszlo Ersek
2019-02-27 12:49 ` Gao, Liming
2019-02-27 19:30 ` Laszlo Ersek
2019-02-28 1:32 ` Gao, Liming
2019-02-28 11:52 ` Laszlo Ersek
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=a41faa3e-170b-00d6-cb19-1e08862a6240@redhat.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