AMD EPYC 9004 Series Processors access control bypass in SEV firmware
A 0-10 score for how bad the bug is in the worst case. It does not say how common the affected setup is.What do these mean? →5.9MediumCNA
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
Firmware for AMD Secure Encrypted Virtualization (SEV) on AMD EPYC 9004, 7003, and 9005 Series Processors has insufficient access control granularity. A local attacker with high privileges, such as a malicious hypervisor, can redirect accesses to MMIO memory, which can compromise guest memory integrity.
Written by a model
Original description
Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially redirect accesses to MMIO memory resulting in loss of guest memory integrity.
What to do
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-2026-0462 (Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to…), 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-2026-0462 (entry last updated 2026-11-21):
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
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-0462 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-0462 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-3059.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-2026-0462
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-0462"}.Affected versions
- AMD AMD EPYC™ 9004 Series Processors
- AMD AMD EPYC™ 7003 Series Processors
- AMD AMD EPYC™ 9005 Series Processors
cve.now Index
11Pof 100 · provisional · methodology v3
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch5/5No fixed version listed; see vendor advisory
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
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | amd.com · en/resources/product-security/bulletin/AMD-SB-3059.html |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-0462 |
| Record | NVD · CVE-2026-0462 |
Related
- CVE-2025-61963Improper input validation within the AmdPlatformRasSmm driver could allow an attacker with privileged access to overwrite SMRAM…
- CVE-2025-0008Insufficient verification of data authenticity may allow a local attacker to bypass Secure Debug Unlock (SDU), potentially resulting in…
- CVE-2024-21954Improper exception handling in IOMMU could allow an invalidate command to be sent to PCIe devices that do not support Address Translation…
- CVE-2024-36344Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access to the Trusted…
- CVE-2026-0436Insufficient parameter sanitization in the AMD Secure Processor (ASP) trusted execution environment (TEE) SPDM driver could allow an…
- CVE-2026-0101Improper validation of specified quantities in input within AMD Power Management Firmware (PMFW) could allow a local attacker to pass…
No corrections so far. Something wrong on this page? Report an error.