AMD hypervisor memory corruption via IOMMU out-of-bounds read

Check whether my systems are affected by CVE-2024-21963 (An out-of-bounds read vulnerability in the IOMMU could allow a malicious guest to corrupt hypervisor (HV) pages and potentially cause a…), 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-2024-21963 (entry last updated 2026-11-13):
Affected:
- AMD AMD EPYC™ 7003 Series Processors: version range not reported
- AMD AMD EPYC™ 7002 Series Processors: version range not reported
- AMD AMD EPYC™ 9004 Series Processors: version range not reported
- AMD AMD EPYC™ 7001 Series Processors: version range not reported
- AMD AMD EPYC™ 4004 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™ 4005 Series Processors: version range not reported
- AMD AMD EPYC™ 8005 Series Processors: version range not reported
- AMD AMD Ryzen™ Threadripper™ PRO 5000 WX-Series Processors: version range not reported
- and 37 more affected products, listed on https://cve.now/CVE-2024-21963
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2024-21963 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-21963 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-4018.html
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3060.html
- http://xenbits.xen.org/xsa/advisory-524.html
- http://www.openwall.com/lists/oss-security/2026/11/10/21
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-2024-21963
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-2024-21963"}.