CVE-2026-60020 · Infrastructure
NO FIX YET
The MigTD virtio-serial driver in Intel's TDX Migration Trust Domain does not free memory after its useful lifetime, so memory is leaked. A privileged local user on the system can exhaust resources and cause a denial of service.
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 systems running Intel TDX with the MigTD Trust Domain and its virtio-serial driver, where a privileged user on the host or guest side can trigger the leak. The sources do not say which MigTD versions are affected or how to confirm the driver is in use, so unknown.
Not affected if no-tdx-migtd
Who cares confidential-computing, intel-tdx, migtd, virtio
Unknown from the sources.
No fix yet, per the sources.
Missing release of memory after effective lifetime in the MigTD virtio-serial driver for the Intel(R) TDX Migration Trust Domain (MigTD) within Ring 0: Hypervisor may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable denial of service. 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 (none) 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:N/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.