CVE-2025-29941 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization (SEV) firmware uses seeds incorrectly in its pseudo-random number generator. A malicious hypervisor or migration agent could import a forged guest context, potentially exposing derived guest keys.
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 hosts running AMD EPYC processors with SEV-enabled virtual machines, where the hypervisor or migration tooling is the attacker's position. The sources do not name affected firmware versions or a patch. Teams not using SEV guests are not exposed.
Not affected if no-sev-guests
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
No fix yet, per the sources.
Incorrect usage of seeds in pseudo-random number generator in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor or migration agent to import a forged guest context potentially resulting in loss of confidentiality for derived guest keys.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/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.