AMD Radeon PRO V620 integer overflow

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.
3.0$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in AMD Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen Threadripper PRO 5000 WX-Series Processors, Ryzen 7030 Mobile Processors with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 4000 Desktop Processors, Ryzen 5000 Desktop Processors, Ryzen Embedded R1000 Processors, Ryzen Embedded R2000 Processors, Ryzen Embedded 5000 Processors, Ryzen Embedded V1000 Processors, Ryzen Embedded V2000 Processors, Ryzen Embedded V3000 Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon RX Vega Graphics Cards, Radeon VII, Radeon PRO W6000 Graphics Products, Radeon PRO WX 8000, 9000 Graphics Cards, Radeon PRO VII, Radeon Instinct MI25, Radeon PRO V520 and Radeon PRO V620. Affected is an unknown function. The manipulation leads to integer overflow. This vulnerability is documented as CVE-2021-26380. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in AMD Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen Threadripper PRO 5000 WX-Series Processors, Ryzen 7030 Mobile Processors with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 4000 Desktop Processors, Ryzen 5000 Desktop Processors, Ryzen Embedded R1000 Processors, Ryzen Embedded R2000 Processors, Ryzen Embedded 5000 Processors, Ryzen Embedded V1000 Processors, Ryzen Embedded V2000 Processors, Ryzen Embedded V3000 Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon RX Vega Graphics Cards, Radeon VII, Radeon PRO W6000 Graphics Products, Radeon PRO WX 8000, 9000 Graphics Cards, Radeon PRO VII, Radeon Instinct MI25, Radeon PRO V520 and Radeon PRO V620. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, and integrity. The summary by CVE is:

A compromised Trusted OS (TOS) driver could issue a malformed call that could potentially allow memory access outside the intended range resulting in loss of integrity.

The advisory is shared at amd.com. The identification of this vulnerability is CVE-2021-26380 since 01/29/2021. The exploitation is known to be difficult. An attack has to be approached locally. The exploitation needs additional levels of successful authentication. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

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: 3.0
VulDB Meta Temp Score: 3.0

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

CVSSv2info

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

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

Exploitinginfo

Class: Integer overflow
CWE: CWE-190 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

01/29/2021 CVE reserved
05/15/2026 +1931 days Advisory disclosed
05/15/2026 +0 days VulDB entry created
05/15/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2021-26380 (🔒)
GCVE (CVE): GCVE-0-2021-26380
GCVE (VulDB): GCVE-100-364121

Entryinfo

Created: 05/15/2026 08:07
Changes: 05/15/2026 08:07 (62)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!