Skip to main content
VulnerabilityPublished

CVE-2024-21961: AMD EPYC™ 7002 Series Processors · Memory Buffer Overflow

Affects AMD EPYC™ 7002 Series ProcessorsSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AMDAMD EPYC™ 7002 Series ProcessorsAffected–Fixed in–
AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ GraphicsAffected–Fixed in–
AMDAMD Ryzen™ 7000 Series Desktop ProcessorsAffected–Fixed in–
AMDAMD Ryzen™ 5000 Series Desktop ProcessorsAffected–Fixed in–
AMDAMD Ryzen™ 3000 Series Desktop ProcessorsAffected–Fixed in–
AMDAMD Ryzen™ Z1 Series ProcessorsAffected–Fixed in–

AI-suggested

Organizations should monitor AMD and their hardware vendors for official firmware or microcode updates addressing CVE-2024-21961 and apply them promptly once available. In the interim, virtualization administrators should implement strict isolation controls between guest VMs and hosts, including limiting PCIe device passthrough and reducing the attack surface by disabling unnecessary PCIe features. Employing hypervisor security best practices such as resource limits, VM escape detection, and continuous monitoring for unusual PCIe activity can help detect exploitation attempts early. Network segmentation and tenant isolation in cloud environments reduce the risk of lateral movement or widespread impact. Additionally, organizations should conduct thorough testing of their virtualization platforms to identify any abnormal behavior related to PCIe operations and prepare incident response plans for potential DoS scenarios. Collaboration with AMD support and hardware vendors is essential to receive timely patches and guidance.

Description

Improper restriction of operations within the bounds of a memory buffer in PCIe® Link could allow an attacker with access to a guest virtual machine to potentially perform a denial of service attack against the host resulting in loss of availability.

References

Community reviews

Loading reviews…