{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-29948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-29948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-29948 is a medium-severity vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-29948 and fix it if it is affected.\n\nWhat it is: CVE-2025-29948 is a medium-severity vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-29948 in the wild and no public exploit code.\n\nAffected product: AMD EPYC™ 9005 Series Processors. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-29948/ (Markdown: https://insights.sbomify.com/CVE-2025-29948/index.md)","id":"CVE-2025-29948","markdown":"https://insights.sbomify.com/CVE-2025-29948/index.md","name":"CVE-2025-29948","record":{"aliases":["GHSA-34ch-j427-vrm7","UBUNTU-CVE-2025-29948"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD EPYC firmware","requires_auth":"high_privilege","summary":"A malicious hypervisor can bypass SEV-SNP memory integrity protections in AMD EPYC firmware, compromising guest memory security.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1260","name":"Improper Handling of Overlap Between Protected Memory Ranges"}],"description":"Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass RMP protections, potentially resulting in a loss of SEV-SNP guest memory integrity.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in AMD EPYC™ 9005 Series Processors","id":"CVE-2025-29948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics","id":"CVE-2025-29949"},"packages":[],"prev":{"headline":"Information disclosure in AMD EPYC™ 9005 Series Processors","id":"CVE-2025-29946"},"products":["AMD EPYC™ 9005 Series Processors","AMD EPYC™ Embedded 9005 Series Processors"],"published":"2026-02-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-11","vendors":["AMD"]},"summary":"A malicious hypervisor can bypass SEV-SNP memory integrity protections in AMD EPYC firmware, compromising guest memory security.","url":"https://insights.sbomify.com/CVE-2025-29948/"}