Incorrect usage of seeds in pseudo-random number generator in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious…
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 11/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The flaw affects AMD Secure Encrypted Virtualization (SEV) firmware, and an attacker with local access and low-privilege login can exploit it without any user action. By abusing incorrectly seeded random number generation, a malicious hypervisor or migration agent could import a forged guest context, which may expose the keys derived for guests to disclosure.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch5/5No patch listed yet
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-29941 (Incorrect usage of seeds in pseudo-random number generator in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2025-29941 (entry last updated 2026-11-10): Affected: - AMD AMD EPYC™ 9004 Series Processors: version range not reported - AMD AMD EPYC™ 7003 Series Processors: version range not reported - AMD AMD EPYC™ 9005 Series Processors: version range not reported - AMD AMD EPYC™ 8004 Series Processors: version range not reported - AMD AMD EPYC™ 8005 Series Processors: version range not reported - AMD AMD EPYC™ Embedded 7003 Series Processors: version range not reported - AMD AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa"): version range not reported - AMD AMD EPYC™ Embedded 9005 Series Processors: version range not reported - AMD AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Bergamo"): version range not reported - AMD AMD EPYC™ Embedded 8004 Series Processors: version range not reported Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2025-29941 is not listed as of cve.now's last read. This KEV status is for CVE-2025-29941 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3038.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2025-29941 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2025-29941.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AMD AMD EPYC™ 9004 Series Processors
Version range not reported
- AMD AMD EPYC™ 7003 Series Processors
Version range not reported
- AMD AMD EPYC™ 9005 Series Processors
Version range not reported
- AMD AMD EPYC™ 8004 Series Processors
Version range not reported
- AMD AMD EPYC™ 8005 Series Processors
Version range not reported
- AMD AMD EPYC™ Embedded 7003 Series Processors
Version range not reported
- AMD AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa")
Version range not reported
- AMD AMD EPYC™ Embedded 9005 Series Processors
Version range not reported
Show all 10 packagesShow fewer packages
- AMD AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Bergamo")
Version range not reported
- AMD AMD EPYC™ Embedded 8004 Series Processors
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.