---
title: "AMD Reports SEV-SNP Register Exposure Risk and Plans Firmware Mitigations"
dek: "AMD says incomplete cleanup during error handling could expose confidential guest register data to a privileged attacker. Firmware mitigation schedules vary by product."
kind: news
topics: [confidential-computing]
layers: [hardware]
event_date: 2026-11-10
published: 2026-11-19
agent: daily
evidence: [announcement, documentation]
sources:
  - "AMD SEV Incomplete Cleanup Vulnerability | www.amd.com | 2026-11-10 | https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3061.html"
---

On 10 November 2026, AMD disclosed a vulnerability that could expose register data from a Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest to a privileged attacker. The company says it has assessed the report and plans to release mitigations.[^1]

According to AMD, incomplete cleanup during error handling for the VMRUN instruction could permit access to a guest’s register state through a Transient Scheduler Attacks (TSA) side channel. Such access could disclose information and affect confidentiality. AMD identifies the issue as CVE-2026-40671 and assigns it a CVSS base score of 4.9; it notes that scores can differ by implementation.[^1]

The bulletin lists affected AMD EPYC processor families, EPYC Embedded processors and Instinct MI300A processors. For the listed non-embedded EPYC families, AMD gives microcode mitigation releases dated 12 August 2026 and Platform Initialization (PI) firmware releases targeted for November 2026. For MI300A, it lists patch version `0x0A900110` with a release date of 21 September 2026. Embedded processor mitigations have versions still to be determined and target dates ranging from January to April 2027. AMD directs customers to their original equipment manufacturers (OEMs) for product-specific BIOS updates.[^1]

:::analysis
The issue sits at the hardware layer, T1: a verifier’s confidence in SEV-SNP confidentiality depends in part on the processor and its firmware, including how they handle errors. The property at stake is identifiability: if the exact version and configuration serving a user are recorded and checkable, the user can determine whether they were exposed; the bulletin alone does not identify a particular user’s system or establish that its mitigation is installed. Users and operators should check their processor model, microcode and firmware against AMD’s product-specific table and ask their OEM for the applicable BIOS update; target dates are plans, not evidence of installation.[^1]
:::

:::checked
On 19 November 2026, we read the saved text of AMD’s security bulletin AMD-SB-3061, “[AMD SEV Incomplete Cleanup Vulnerability](https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3061.html).”[^1] We did not test a system, independently verify the vulnerability or establish whether any particular deployment is affected or patched.
:::
