When new FV is installed, VerifyFv() should be invoked to do security checking for...

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@5785 6f19259b-4bc3-4df7-8a09-765794883524

diff --git a/MdeModulePkg/Core/Pei/FwVol/FwVol.c b/MdeModulePkg/Core/Pei/FwVol/FwVol.c
index cf0cfe78c5c12e6aa7530298df3d695bd078fd1b..f2b5cedd361b0038db287f6b6fe8ad53cce376a2 100644 (file)
--- a/MdeModulePkg/Core/Pei/FwVol/FwVol.c
+++ b/MdeModulePkg/Core/Pei/FwVol/FwVol.c
@@ -307,6 +307,7 @@ PeiInitializeFv (
   @param Ppi               Address of the PPI that was installed.\r
 \r
   @retval EFI_SUCCESS    The FV Info is registered into PeiCore private data structure.\r
+  @return if not EFI_SUCESS, fail to verify FV.\r
 \r
 **/\r
 EFI_STATUS\r
@@ -342,6 +343,13 @@ FirmwareVolmeInfoPpiNotifyCallback (
         return EFI_SUCCESS;\r
       }\r
     }\r
+    \r
+    Status = VerifyFv ((EFI_FIRMWARE_VOLUME_HEADER*)Fv->FvInfo);\r
+    if (EFI_ERROR(Status)) {\r
+      DEBUG ((EFI_D_ERROR, "Fail to verify FV which address is 0x%11p", (VOID *) Fv->FvInfo));\r
+      return Status;\r
+    }\r
+    \r
     PrivateData->Fv[PrivateData->FvCount++].FvHeader = (EFI_FIRMWARE_VOLUME_HEADER*)Fv->FvInfo;\r
 \r
     //\r