AMD Ryzen Embedded V3000 Crash Defender denial of service

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

Summaryinfo

A vulnerability was found in AMD Ryzen 5000 Desktop Processors, Ryzen 5000 Desktop Processor with Radeon Graphics, Ryzen 7000 Desktop Processors, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 4000 Desktop Processor with Radeon Graphics, Ryzen 8000 Processor with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 3000 Mobile Processor with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 5000 Processors with Radeon Graphics, Ryzen 7020 Processors with Radeon Graphics, Ryzen 6000 Processor with Radeon Graphics, Ryzen 7035 Processor with Radeon Graphics, Ryzen 7030 Processors with Radeon Graphics, Ryzen 7040 Processors with Radeon Graphics, Ryzen 7045 Mobile Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 7000 Graphics Products, Radeon PRO W7000 Graphics Products, Radeon VII, Radeon PRO VII, Radeon Instinct MI25, Radeon PRO V520, Radeon PRO V620, Radeon PRO V710, Ryzen Embedded R1000, Ryzen Embedded R2000, Ryzen Embedded 7000, Ryzen Embedded V1000, Ryzen Embedded V2000 and Ryzen Embedded V3000. It has been rated as problematic. Impacted is an unknown function of the component Crash Defender. The manipulation leads to denial of service. This vulnerability is documented as CVE-2024-21971. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in AMD Ryzen 5000 Desktop Processors, Ryzen 5000 Desktop Processor with Radeon Graphics, Ryzen 7000 Desktop Processors, Athlon 3000 Desktop Processors with Radeon Graphics, Ryzen 4000 Desktop Processor with Radeon Graphics, Ryzen 8000 Processor with Radeon Graphics, Athlon 3000 Mobile Processors with Radeon Graphics, Ryzen 3000 Mobile Processor with Radeon Graphics, Ryzen 4000 Mobile Processors with Radeon Graphics, Ryzen 5000 Processors with Radeon Graphics, Ryzen 7020 Processors with Radeon Graphics, Ryzen 6000 Processor with Radeon Graphics, Ryzen 7035 Processor with Radeon Graphics, Ryzen 7030 Processors with Radeon Graphics, Ryzen 7040 Processors with Radeon Graphics, Ryzen 7045 Mobile Processors, Radeon RX 5000 Graphics Products, Radeon PRO W5000 Graphics Products, Radeon RX 7000 Graphics Products, Radeon PRO W7000 Graphics Products, Radeon VII, Radeon PRO VII, Radeon Instinct MI25, Radeon PRO V520, Radeon PRO V620, Radeon PRO V710, Ryzen Embedded R1000, Ryzen Embedded R2000, Ryzen Embedded 7000, Ryzen Embedded V1000, Ryzen Embedded V2000 and Ryzen Embedded V3000 and classified as problematic. This issue affects an unknown function of the component Crash Defender. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:

Improper input validation in AMD Crash Defender could allow an attacker to provide the Windows® system process ID to a kernel-mode driver, resulting in an operating system crash, potentially leading to denial of service.

The advisory is shared at amd.com. The identification of this vulnerability is CVE-2024-21971 since 01/03/2024. The exploitation is known to be easy. An attack has to be approached locally. 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-19577). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector (AMD): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Denial of service
CWE: 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/03/2024 🔍
02/12/2025 +406 days 🔍
02/12/2025 +0 days 🔍
09/24/2025 +224 days 🔍

Sourcesinfo

Advisory: amd.com
Status: Confirmed

CVE: CVE-2024-21971 (🔍)
GCVE (CVE): GCVE-0-2024-21971
GCVE (VulDB): GCVE-100-295421
EUVD: 🔍

Entryinfo

Created: 02/12/2025 08:30
Updated: 09/24/2025 04:46
Changes: 02/12/2025 08:30 (61), 09/24/2025 00:38 (1), 09/24/2025 04:46 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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!