[Bug 3513] New: MOR bit heuristic in Variable/RuntimeDxe/TcgMorLockSmm.c incompatible with StandaloneMM



Bug ID: 3513
Summary: MOR bit heuristic in
Variable/RuntimeDxe/TcgMorLockSmm.c incompatible with
Product: EDK2
Version: Current
Hardware: All
OS: All
Severity: normal
Priority: Lowest
Component: Code
Assignee: unassigned@tianocore.org
Reporter: jerecox@microsoft.com
CC: edk2+bugs+int+994+563148131503455288@groups.io

In Variable/RuntimeDxe/TcgMorLockSmm.c, it calls VariableHaveTcgProtocols() to
determine if TCG protocols are present. If FALSE is returned, it assumes the
BIOS does not support the TCG Reset Attack Mitigation, deletes the MOR bit, and
locks the variable so that OS cannot create it. This is documented as follows:

// Some OSes don't follow the TCG's Platform Reset Attack Mitigation spec
// in that the OS should never create the MOR variable, only read and write
// it -- these OSes (unintentionally) create MOR if the platform firmware
// does not produce it. Whether this is the case (from the last OS boot)
// can be deduced from the absence of the TCG / TCG2 protocols, as edk2's
// MOR implementation depends on (one of) those protocols.

I support the MOR bit, but StandaloneMm does not support locating/calling these
protocols, thus it returns FALSE in:


We need a StandaloneMm compatible mechanism of signaling support of TCG Reset
Attack Mitigation.

You are receiving this mail because:
You are on the CC list for the bug.