System Management Mode (SMM):
SMM is entered via the SMI (system management interrupt), which is invoked by:
- Motherboard hardware or chipset signaling via a designated pin SMI# of the processor chip. This signal can be an independent event.
- Software SMI triggered by the system software via an I/O access to a location considered special by the motherboard logic (port 0B2h is
common).
- An I/O write to a location which the firmware has requested that the processor chip act on.
This means that triggering SMM is a motherboard function, so depending on the
motherboard firmware to be either enabled or not.
The motherboard firmware itself is digitally protected from modification.
SMM is specifically not an
Intel Management Engine (ME)
function.
The SMM code that is triggered is part of the BIOS, which itself cannot
be modified without possessing the manufacturer's digital key.
SMM can however be subverted by changing the SMI interrupt address
to point to code introduced by the attacker.
All these actions require the attacker to operate inside kernel mode
in order to subvert the SMI address and SMM code, and exploits do exist
for that, as you have noted above.
However, beside the intellectual satisfaction of such an exploit, its utility
is doubtful:
- Any SMM exploit will not survive a reboot
- Subverting SMM requires the attacker to operate in kernel space,
therefore to already be in control of the computer
- The SMI interrupt is not called by Windows, so subverting it is not useful.
My belief is that disabling or disactivating SMM is not possible,
but its presence in your computer (if it's present) is not a vulnerability
that an attacker would need (or bother) to attack.
Because SMM is opaque to the operating system, it is not possible to test
in Windows its presence or its correct functionality.
Microsoft requires motherboard vendors to deliver a robust and secure
platform, where SMM code was carefully analyzed and protected.
To that effect, the vendor must confirm to Windows via the ACPI
that certain security best practices have been implemented in SMM.
For details see the article
Understanding the Windows SMM Security Mitigation Table (WSMT).