SMM Code Caching and Validation to Prevent Cache Poisoning

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Information handling systems, particularly in SMM mode, are vulnerable to cache poisoning and malware attacks, leading to increased boot times and risks of data compromise, as existing solutions require unzipping SMM Code at each boot-up and lack effective validation mechanisms for updates.

Innovation Solution

The method involves detecting the completion of a power-on self-test (POST) routine to unzip and store SMM Code in persistent memory, allowing for secure updates using signed images, and validating updates before replacing cached copies, thereby preventing cache poisoning and speeding up boot times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If SMM Code is stored in cacheable memory for fast access, then boot time is reduced, but the system becomes vulnerable to cache poisoning attacks where cached instructions are replaced with harmful code

Engineering Contradiction:

Improveboot timeVSAvoidsecurity against cache poisoning

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The patent divides SMM Code into multiple segments: a compressed version stored in BIOS flash memory and an uncompressed cached version stored in persistent memory. This segmentation allows the system to load only necessary portions into cache, reducing the attack surface for cache poisoning while maintaining fast boot performance for critical code segments.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary validation of SMM Code during the POST routine before it is executed from cache. By validating the compressed code from flash memory against the cached version and verifying integrity signatures in advance, the system prevents cache poisoning attacks before they can compromise system security, while still allowing cached code to be used for fast boot.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If SMM Code is unzipped from BIOS flash memory at each boot-up to ensure freshness, then security is improved, but boot time increases significantly

Engineering Contradiction:

ImprovesecurityVSAvoidboot time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements periodic validation of cached SMM Code during POST routines instead of unzipping at every boot. The system validates the cached code against the compressed source in flash memory at scheduled intervals (periodic POST routines), ensuring security while avoiding the performance penalty of full decompression at each boot. Validated cached code can then be used for subsequent boots until the next validation cycle.

Inventive Principle:

Principle #19Periodic action

3Reliability

If update validation mechanisms are implemented for SMM Code, then security against malware injection is improved, but the update process complexity increases

Engineering Contradiction:

Improvesecurity against malwareVSAvoidupdate process

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the system continuously monitors and validates SMM Code integrity through signature verification and comparison between compressed and uncompressed versions. This automated feedback loop detects potential malware injections and prevents execution of compromised code, providing robust security without requiring complex manual update procedures. The validation feedback is integrated into the existing POST routine, minimizing additional complexity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS10101928B2System and method for enhanced security and update of SMM to prevent malware injection

Publication Date: 2018.10.16 DELL PROD LP

AI summary

An information handling system for enhanced system management mode (SMM) security may include a processor, system management random access memory (SMRAM), persistent memory, and basic input/output (BIOS) memory. The system may include instructions that, when loaded and executed by the processor, cause the processor to initialize the memory, initialize the BIOS memory, initialize the persistent memory, and check whether the system has previously executed a power-on self test (POST) routine. Based on a determination that the system has not previously executed a POST routine, the processor may unzip the SMM Code located in the BIOS memory store the unzipped SMM Code in the persistent memory and in the SMRAM. Based on a determination that the system has previously executed a POST routine, the processor may create a duplicate copy of the SMM Code from the persistent memory and store the duplicate copy in the SMRAM. The processor may further initialize the SMRAM, lock the SMRAM, and hide the SMM Code stored in the persistent memory.