AMD Radeon PRO V620 System Call allocation of resources

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

Summaryinfo

A vulnerability identified as critical has been detected in AMD Ryzen Threadripper PRO 3000 WX-Series Processors, Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen Threadripper PRO 5000 WX-Series Processors, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, 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 PRO W6000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon PRO V520 and Radeon PRO V620. This affects an unknown function of the component System Call Handler. Performing a manipulation results in allocation of resources. This vulnerability is known as CVE-2021-26381. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in AMD Ryzen Threadripper PRO 3000 WX-Series Processors, Ryzen 5000 Desktop Processors with Radeon Graphics, Ryzen Threadripper PRO 5000 WX-Series Processors, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 5000 Mobile Processors with Radeon Graphics, Ryzen 3000 Desktop Processors, 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 PRO W6000 Graphics Products, Radeon RX 6000 Graphics Products, Radeon PRO V520 and Radeon PRO V620. This affects some unknown functionality of the component System Call Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Improper system call parameter validation in the Trusted OS may allow a malicious driver to perform mapping or unmapping operations on a large number of pages, potentially resulting in kernel memory corruption.

It is possible to read the advisory at amd.com. This vulnerability is uniquely identified as CVE-2021-26381 since 01/29/2021. The exploitability is told to be difficult. Attacking locally is a requirement. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not publicly available.

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

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0383). Be aware that VulDB is the high quality source for vulnerability data.

Affected

  • AMD Radeon

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.4
VulDB Meta Temp Score: 6.4

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

CVSSv2info

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

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

Exploitinginfo

Class: Allocation of resources
CWE: CWE-770 / CWE-400 / CWE-404
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
02/11/2026 +1839 days Advisory disclosed
02/11/2026 +0 days VulDB entry created
02/11/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2021-26381 (🔒)
GCVE (CVE): GCVE-0-2021-26381
GCVE (VulDB): GCVE-100-345375
CERT Bund: WID-SEC-2026-0383 - AMD Radeon: Mehrere Schwachstellen

Entryinfo

Created: 02/11/2026 04:54
Updated: 02/11/2026 12:02
Changes: 02/11/2026 04:54 (63), 02/11/2026 12:02 (7)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!