AMD EPYC 7001 Processors memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in AMD EPYC 7001 Processors, EPYC 7002 Processors, EPYC 7003 Processors, EPYC 8004 Processors, EPYC 9004 Processors, EPYC 9005 Processors, EPYC Embedded 3000 Processors, EPYC Embedded 7002 Processors, EPYC Embedded 7003 Processors, EPYC Embedded 8004 Processors, EPYC Embedded 9004 Processor, EPYC Embedded 9005 Processors, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, Ryzen 3000 Mobile Processors with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 6000 Processors with Radeon Graphics, Ryzen 7000 Desktop Processors, Ryzen 7020 Processors with Radeon Graphics, Ryzen 7040 Mobile Processors with Radeon Graphics, Ryzen 7045 Mobile Processors with Radeon Graphics, Ryzen 8000 Desktop Processors, Ryzen Threadripper PRO 3000 WX-Series Processors, Ryzen Threadripper PRO 5000 WX-Series Processors, Ryzen Embedded 5000 Processors, Ryzen Embedded 7000 Processors, Ryzen Embedded 8000 Processors, Ryzen Embedded R1000 Processors, Ryzen Embedded R2000 Processors, Ryzen Embedded V1000 Processors, Ryzen Embedded V2000 Processors and Ryzen Embedded V3000 Processors. This vulnerability affects unknown code. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2023-31364. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in AMD EPYC 7001 Processors, EPYC 7002 Processors, EPYC 7003 Processors, EPYC 8004 Processors, EPYC 9004 Processors, EPYC 9005 Processors, EPYC Embedded 3000 Processors, EPYC Embedded 7002 Processors, EPYC Embedded 7003 Processors, EPYC Embedded 8004 Processors, EPYC Embedded 9004 Processor, EPYC Embedded 9005 Processors, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, Ryzen 3000 Mobile Processors with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 6000 Processors with Radeon Graphics, Ryzen 7000 Desktop Processors, Ryzen 7020 Processors with Radeon Graphics, Ryzen 7040 Mobile Processors with Radeon Graphics, Ryzen 7045 Mobile Processors with Radeon Graphics, Ryzen 8000 Desktop Processors, Ryzen Threadripper PRO 3000 WX-Series Processors, Ryzen Threadripper PRO 5000 WX-Series Processors, Ryzen Embedded 5000 Processors, Ryzen Embedded 7000 Processors, Ryzen Embedded 8000 Processors, Ryzen Embedded R1000 Processors, Ryzen Embedded R2000 Processors, Ryzen Embedded V1000 Processors, Ryzen Embedded V2000 Processors and Ryzen Embedded V3000 Processors. It has been rated as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. The summary by CVE is:

Improper handling of direct memory writes in the input-output memory management unit could allow a malicious guest virtual machine (VM) to flood a host with writes, potentially causing a fatal machine check error resulting in denial of service.

The advisory is shared at amd.com. The identification of this vulnerability is CVE-2023-31364 since 04/27/2023. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.

Upgrading eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Timelineinfo

04/27/2023 CVE reserved
02/26/2026 +1036 days Advisory disclosed
02/26/2026 +0 days VulDB entry created
02/26/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2023-31364 (🔒)
GCVE (CVE): GCVE-0-2023-31364
GCVE (VulDB): GCVE-100-348065

Entryinfo

Created: 02/26/2026 22:22
Changes: 02/26/2026 22:22 (64)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!