What is the CVSS score of CVE-2023-20548?

CVE-2023-20548 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2023-20548?

Within 24 hours: Identify all systems running ROCm and assess business criticality; notify stakeholders of the vulnerability and interim restrictions. Within 7 days: Implement network segmentation to isolate ROCm-dependent systems from trusted networks; disable ROCm features if not operationally critical. Within 30 days: Monitor AMD's patch release timeline; establish testing procedures for the patch once available; conduct vulnerability rescans post-remediation.

Radeon Pro Vii Firmware CVE-2023-20548

HIGH

Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

2026-02-11 psirt@amd.com

Race Condition Amd Radeon Pro Vii Firmware Radeon Software Radeon Vii Firmware Rocm

7.8

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-367 OWASP Top 10:2025 A04:2021 - Insecure Design ASVS 5.0 V15 - Secure Coding and Architecture TOCTOU prevention
Impact	CVSS 7.8 (HIGH). Attack vector: Local. Complexity: High. Privileges required: Low. User interaction: None.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to corrupt memory resulting in loss of integrity, confidentiality, or availability.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Rocm contains a vulnerability that allows attackers to corrupt memory resulting in loss of integrity, confidentiality, or availability (CVSS 7.8).

RemediationAI

Monitor vendor advisories for a patch.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

affects Rocm. A Time-of-check time-of-use (TOCTOU) race condition in the AMD Secure Processor (ASP) could allow an attacker to corrupt memory resulting in loss of integrity, confidentiality, or availability.

Know when Radeon Pro Vii Firmware gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH

AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

A Time-of-check time-of-use (TOCTOU) race condition in the AMD Secure Processor (ASP) could allow an attacker to corrupt memory resulting in loss of integrity, confidentiality, or availability.

Executive ViewAI

Why It Matters

CVE-2023-20548 affects ROCm (AMD's open-source compute platform) and enables memory corruption attacks that could compromise data integrity and system availability. Organizations using ROCm for GPU computing, machine learning, or high-performance computing workloads face potential data breach and service disruption risks until mitigation is deployed.

Business Impact: High

Compensating Controls

Network segmentation to restrict ROCm system access; disable GPU compute features if feasible; implement strict input validation on applications interfacing with ROCm; restrict user/process privileges on affected systems; monitor for suspicious memory access patterns via EDR tools; maintain air-gapped environments for critical ROCm workloads until patch availability.

Threat Intelligence Overview

EPSS Score

0.0%

Top 97% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Small

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +39

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Race Condition MEDIUM

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).