Database/Firmware, BMC & network fabric
Intel TDX MigTD: integer overflow in vsock lets a low-privileged local user crash MigTD
Impact
An integer overflow in MigTD's vsock code lets an unprivileged but authenticated local user crash MigTD (high availability impact) with limited data corruption (low integrity impact). Exploitation is high complexity. The likely result is a failed TD live migration. The record does not say which local user can reach the vsock path.
Who can reach it
Local authenticated user with low privileges (PR:L) on the TDX host. High complexity, no user interaction.
What to do
Apply the MigTD update named in Intel advisory INTEL-SA-01580. The record does not give a fixed version. Rollout cost depends on how your VMM stack deploys the MigTD image.
References
Related entries
- Lenovo XClarity Essentials OneCLI: crafted remote path injects OS commands on managed serversCVE-2026-65952 · Lenovo XClarity Essentials OneCLI for Linux (remote SSH operation)Medium
- Arista EOS (tunnel decapsulation): With VXLAN, decap-groups or GRE configured, the switch incorrectly decapsulates andCVE-2026-7473 · Arista EOS (tunnel decapsulation)Medium
- GRUB2 (initrd size handling): Integer overflows in the initrd command's size arithmetic corrupt GRUB's heapCVE-2020-15707 · GRUB2 (initrd size handling)Medium
- GRUB2 (PNG grayscale reader): Out-of-bounds write on the grayscale PNG pathCVE-2021-3696 · GRUB2 (PNG grayscale reader)Medium
- AMI MegaRAC SPx (BMC web interface, HTTP header handling): CRLF sequences are not neutralised in HTTP headers, soCVE-2023-34472 · AMI MegaRAC SPx (BMC web interface, HTTP header handling)Medium
- AMD Secure Processor - cryptographic key usage control: Once an attacker has arbitrary code execution inside the ASPCVE-2024-21981 · AMD Secure Processor - cryptographic key usage controlMedium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.