MIGTD · CVE-2026-61467 · Infrastructure
NO FIX YET
A use-after-free bug in the virtio driver of Intel's TDX Migration Trust Domain (MigTD) can corrupt data and may let a privileged local user escalate privileges. The sources describe the impact as high integrity loss and low availability loss, with no confidentiality impact.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects Intel TDX deployments that run the MigTD component with its virtio driver, a Trust Domain used for live migration of confidential VMs. The sources do not name affected versions or a configuration that makes it reachable. Teams not running Intel TDX migration can skip it.
Not affected if no-intel-tdx
Who cares confidential-computing, intel-tdx, migtd, virtualization
Unknown from the sources.
No fix yet, per the sources.
Use after free in the MigTD virtio driver for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable data corruption. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (high) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.