AMD’s Controversial Decision on TSME in Consumer CPUs
In recent discussions surrounding AMD’s CPU features, an unsettling revelation has emerged regarding the company’s transparent memory encryption (TSME) capabilities for consumer processors. Responding to inquiries, AMD representative Limoncello stated, “My apologies; but I don’t have any more information to share on this topic.” This swift closure of the conversation left many users, including Kilpatrick, feeling frustrated and seeking clarity.
The Origin of the Confusion
The initial mention of TSME in AMD consumer CPUs dates back to a comment by engineer Lendacky in 2020. In a thread about encryption features in AMD processors, Lendacky asserted that the Ryzen 3700x, a consumer CPU, “should support TSME.” This comment was revisited in 2025, where he advised users to enable TSME in their BIOS for enhanced security.
Interestingly, AMD has never explicitly marketed TSME for consumer CPUs. Instead, the company has consistently indicated that its related memory protection feature, Secure Memory Encryption (SME), is reserved for its Pro and Epyc CPU tiers. SME operates on a single key managed by the operating system to selectively encrypt memory pages. In contrast, TSME is firmware-managed, encrypting all RAM without OS involvement, thereby offering a higher level of protection against various physical attacks, including cold boot exploits and DRAM snooping.
User Reactions and Concerns
The lack of marketing surrounding TSME in consumer CPUs, coupled with engineers’ earlier comments, has understandably led users like Kilpatrick to believe that this feature was a standard inclusion. The sudden removal of TSME, without acknowledgment or explanation from AMD, feels like a breach of trust, as many users had come to rely on it for enhanced data security.
Joe Fitzgerald, an authority on silicon-level security, expressed his sentiments regarding AMD’s situation in an interview: “They could have not realized they did it, leading to their cagey responses, or they could have done it intentionally and tried to get away with it, leading to the same cagey responses. But I really feel like an explanation should be in order, even if it was ‘TSME was never supposed to be supported. We did ship some firmwares that erroneously enabled it, but you shouldn’t use them since we can’t guarantee it’ll work properly.’”
As the situation unfolds, the tech community awaits a more comprehensive response from AMD. Users are keen to understand the rationale behind the unexpected removal of TSME, especially considering its implications for data security in consumer-grade products.
For further insights into this developing story, check out the full article here.
Image Credit: arstechnica.com
