MdeModulePkg: Change TCG MOR variables to use VariablePolicy

[mirror_edk2.git] / MdeModulePkg / Universal / Variable / RuntimeDxe / TcgMorLockDxe.c

/** @file\r
  TCG MOR (Memory Overwrite Request) Lock Control support (DXE version).\r
\r
  This module clears MemoryOverwriteRequestControlLock variable to indicate\r
  MOR lock control unsupported.\r
\r
Copyright (c) 2016, Intel Corporation. All rights reserved.<BR>\r
Copyright (c) Microsoft Corporation.\r
SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
**/\r
\r
#include <PiDxe.h>\r
#include <Guid/MemoryOverwriteControl.h>\r
#include <IndustryStandard/MemoryOverwriteRequestControlLock.h>\r
#include <Library/DebugLib.h>\r
#include <Library/BaseLib.h>\r
#include <Library/BaseMemoryLib.h>\r
#include "Variable.h"\r
\r
#include <Protocol/VariablePolicy.h>\r
#include <Library/VariablePolicyHelperLib.h>\r
\r
/**\r
  This service is an MOR/MorLock checker handler for the SetVariable().\r
\r
  @param[in]  VariableName the name of the vendor's variable, as a\r
                           Null-Terminated Unicode String\r
  @param[in]  VendorGuid   Unify identifier for vendor.\r
  @param[in]  Attributes   Attributes bitmask to set for the variable.\r
  @param[in]  DataSize     The size in bytes of Data-Buffer.\r
  @param[in]  Data         Point to the content of the variable.\r
\r
  @retval  EFI_SUCCESS            The MOR/MorLock check pass, and Variable\r
                                  driver can store the variable data.\r
  @retval  EFI_INVALID_PARAMETER  The MOR/MorLock data or data size or\r
                                  attributes is not allowed for MOR variable.\r
  @retval  EFI_ACCESS_DENIED      The MOR/MorLock is locked.\r
  @retval  EFI_ALREADY_STARTED    The MorLock variable is handled inside this\r
                                  function. Variable driver can just return\r
                                  EFI_SUCCESS.\r
**/\r
EFI_STATUS\r
SetVariableCheckHandlerMor (\r
  IN CHAR16     *VariableName,\r
  IN EFI_GUID   *VendorGuid,\r
  IN UINT32     Attributes,\r
  IN UINTN      DataSize,\r
  IN VOID       *Data\r
  )\r
{\r
  //\r
  // Just let it pass. No need provide protection for DXE version.\r
  //\r
  return EFI_SUCCESS;\r
}\r
\r
/**\r
  Initialization for MOR Control Lock.\r
\r
  @retval EFI_SUCCESS     MorLock initialization success.\r
  @return Others          Some error occurs.\r
**/\r
EFI_STATUS\r
MorLockInit (\r
  VOID\r
  )\r
{\r
  //\r
  // Always clear variable to report unsupported to OS.\r
  // The reason is that the DXE version is not proper to provide *protection*.\r
  // BIOS should use SMM version variable driver to provide such capability.\r
  //\r
  VariableServiceSetVariable (\r
    MEMORY_OVERWRITE_REQUEST_CONTROL_LOCK_NAME,\r
    &gEfiMemoryOverwriteRequestControlLockGuid,\r
    0,                                          // Attributes\r
    0,                                          // DataSize\r
    NULL                                        // Data\r
    );\r
\r
  //\r
  // The MOR variable can effectively improve platform security only when the\r
  // MorLock variable protects the MOR variable. In turn MorLock cannot be made\r
  // secure without SMM support in the platform firmware (see above).\r
  //\r
  // Thus, delete the MOR variable, should it exist for any reason (some OSes\r
  // are known to create MOR unintentionally, in an attempt to set it), then\r
  // also lock the MOR variable, in order to prevent other modules from\r
  // creating it.\r
  //\r
  VariableServiceSetVariable (\r
    MEMORY_OVERWRITE_REQUEST_VARIABLE_NAME,\r
    &gEfiMemoryOverwriteControlDataGuid,\r
    0,                                      // Attributes\r
    0,                                      // DataSize\r
    NULL                                    // Data\r
    );\r
\r
  return EFI_SUCCESS;\r
}\r
\r
/**\r
  Delayed initialization for MOR Control Lock at EndOfDxe.\r
\r
  This function performs any operations queued by MorLockInit().\r
**/\r
VOID\r
MorLockInitAtEndOfDxe (\r
  VOID\r
  )\r
{\r
  EFI_STATUS                        Status;\r
  EDKII_VARIABLE_POLICY_PROTOCOL    *VariablePolicy;\r
\r
  // First, we obviously need to locate the VariablePolicy protocol.\r
  Status = gBS->LocateProtocol( &gEdkiiVariablePolicyProtocolGuid, NULL, (VOID**)&VariablePolicy );\r
  if (EFI_ERROR( Status )) {\r
    DEBUG(( DEBUG_ERROR, "%a - Could not locate VariablePolicy protocol! %r\n", __FUNCTION__, Status ));\r
    return;\r
  }\r
\r
  // If we're successful, go ahead and set the policies to protect the target variables.\r
  Status = RegisterBasicVariablePolicy( VariablePolicy,\r
                                        &gEfiMemoryOverwriteRequestControlLockGuid,\r
                                        MEMORY_OVERWRITE_REQUEST_CONTROL_LOCK_NAME,\r
                                        VARIABLE_POLICY_NO_MIN_SIZE,\r
                                        VARIABLE_POLICY_NO_MAX_SIZE,\r
                                        VARIABLE_POLICY_NO_MUST_ATTR,\r
                                        VARIABLE_POLICY_NO_CANT_ATTR,\r
                                        VARIABLE_POLICY_TYPE_LOCK_NOW );\r
  if (EFI_ERROR( Status )) {\r
    DEBUG(( DEBUG_ERROR, "%a - Could not lock variable %s! %r\n", __FUNCTION__, MEMORY_OVERWRITE_REQUEST_CONTROL_LOCK_NAME, Status ));\r
  }\r
  Status = RegisterBasicVariablePolicy( VariablePolicy,\r
                                        &gEfiMemoryOverwriteControlDataGuid,\r
                                        MEMORY_OVERWRITE_REQUEST_VARIABLE_NAME,\r
                                        VARIABLE_POLICY_NO_MIN_SIZE,\r
                                        VARIABLE_POLICY_NO_MAX_SIZE,\r
                                        VARIABLE_POLICY_NO_MUST_ATTR,\r
                                        VARIABLE_POLICY_NO_CANT_ATTR,\r
                                        VARIABLE_POLICY_TYPE_LOCK_NOW );\r
  if (EFI_ERROR( Status )) {\r
    DEBUG(( DEBUG_ERROR, "%a - Could not lock variable %s! %r\n", __FUNCTION__, MEMORY_OVERWRITE_REQUEST_VARIABLE_NAME, Status ));\r
  }\r
\r
  return;\r
}\r