From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: edk2-devel@lists.01.org
Subject: Re: [Patch 1/2] MdeModulePkg/IScsiDxe: Set ExitBootServiceEvent to NULL after close it.
Date: Tue, 9 Jan 2018 11:45:49 +0800 [thread overview]
Message-ID: <a2df41c1-f4d1-25d6-3484-d2a08cdb4086@Intel.com> (raw)
In-Reply-To: <1515466566-13136-2-git-send-email-jiaxin.wu@intel.com>
On 1/9/2018 10:56 AM, Jiaxin Wu wrote:
> There are two place to close the ISCSI ExitBootServiceEvent:
> One is IScsiOnExitBootService callback function.
> Another is ISCSI driver stop() function.
>
> When OS loader triggers ExitBootServiceEvent, firstly, the exit boot service
> callback function will close and free the ExitBootServiceEvent, then secondly
> the system will call ISCSI driver stop() function, the ExitBootServiceEvent
> will be closed and freed again, the use-after-free memory access happens.
>
> This issue is recorded at https://bugzilla.tianocore.org/show_bug.cgi?id=742.
> This patch is to resolve the issue.
>
> Cc: Ye Ting <ting.ye@intel.com>
> Cc: Fu Siyuan <siyuan.fu@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Wu Jiaxin <jiaxin.wu@intel.com>
> ---
> MdeModulePkg/Universal/Network/IScsiDxe/IScsiMisc.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/MdeModulePkg/Universal/Network/IScsiDxe/IScsiMisc.c b/MdeModulePkg/Universal/Network/IScsiDxe/IScsiMisc.c
> index ae202c3..29dfe94 100644
> --- a/MdeModulePkg/Universal/Network/IScsiDxe/IScsiMisc.c
> +++ b/MdeModulePkg/Universal/Network/IScsiDxe/IScsiMisc.c
> @@ -1,9 +1,9 @@
> /** @file
> Miscellaneous routines for iSCSI driver.
>
> -Copyright (c) 2004 - 2016, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2004 - 2018, Intel Corporation. All rights reserved.<BR>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions of the BSD License
> which accompanies this distribution. The full text of the license may be found at
> http://opensource.org/licenses/bsd-license.php
>
> @@ -622,13 +622,14 @@ IScsiCleanDriverData (
> &Private->IScsiExtScsiPassThru
> );
> }
>
> EXIT:
> -
> - gBS->CloseEvent (Private->ExitBootServiceEvent);
> -
> + if (Private->ExitBootServiceEvent != NULL) {
> + gBS->CloseEvent (Private->ExitBootServiceEvent);
> + }
> +
> FreePool (Private);
> return Status;
> }
>
> /**
> @@ -870,12 +871,15 @@ IScsiOnExitBootService (
> )
> {
> ISCSI_DRIVER_DATA *Private;
>
> Private = (ISCSI_DRIVER_DATA *) Context;
> +
> gBS->CloseEvent (Private->ExitBootServiceEvent);
>
> + Private->ExitBootServiceEvent = NULL;
> +
> IScsiSessionAbort (&Private->Session);
> }
>
> /**
> Tests whether a controller handle is being managed by IScsi driver.
>
Jiaxin,
I agree your patch can fix the use-after-free issue in your network
driver.
But I think a more root fix should be in CoreCloseEvent().
You could refer to CoreValidateHandle(). It looks for the
Handle in handle database for a match before deferencing it.
--
Thanks,
Ray
next prev parent reply other threads:[~2018-01-09 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 2:56 [Patch 0/2] IScsiDxe: Set ExitBootServiceEvent to NULL after close it Jiaxin Wu
2018-01-09 2:56 ` [Patch 1/2] MdeModulePkg/IScsiDxe: " Jiaxin Wu
2018-01-09 3:45 ` Ni, Ruiyu [this message]
2018-01-09 2:56 ` [Patch 2/2] NetworkPkg/IScsiDxe: " Jiaxin Wu
2018-01-09 6:14 ` [Patch 0/2] IScsiDxe: " Fu, Siyuan
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=a2df41c1-f4d1-25d6-3484-d2a08cdb4086@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