Radeon SoftwareApplication · Amd

CVE-2023-31320

HIGH · 7.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 23.q3 / 23.7.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in the AMD RadeonTM Graphics display driver may allow an attacker to corrupt the display potentially resulting in denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Improper input validation in AMD Radeon Graphics display drivers allows potentially malicious or malformed input data to be processed by the driver, leading to display corruption and denial of service conditions.

MitigationApply AMD vendor-supplied graphics driver updates to patch the input validation vulnerability; organizations should inventory affected systems and deploy tested driver updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Radeon SoftwareApplication
Affected:< 23.7.1< 23.q3
Radeon Rx Vega 56 FirmwareOperating system
Affected:all versions
Radeon Rx Vega 64 FirmwareOperating system
Affected:all versions
Radeon Pro Vega 56 FirmwareOperating system
Affected:all versions
Radeon Pro Vega 64 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AMD GPU model
    Open Device Manager, expand 'Display adapters', and note the exact AMD GPU model name (e.g., Radeon RX Vega 56, Radeon RX Vega 64, Radeon Pro Vega 56, Radeon Pro Vega 64)
    Affected if The GPU is any of the four listed Vega models (RX Vega 56, RX Vega 64, Pro Vega 56, Pro Vega 64)
  2. Check AMD Radeon Software driver version on Windows
    Open AMD Radeon Software, click the gear icon, select 'System' > 'Software', and note the 'Driver Version' displayed (or run 'dxdiag' and check the display driver version under the Notes tab)
    Affected if The driver version is lower than 23.7.1 (or lower than the 23.q3 release if that naming applies)
  3. Check driver version via PowerShell or CLI
    Run 'Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion' in PowerShell to retrieve the installed display driver version
    Affected if The reported driver version is lower than 23.7.1
  4. Verify firmware version for affected Vega GPUs
    For systems with Vega 56/64 GPUs, check the VBIOS/firmware version through AMD Radeon Software 'Performance' tab > 'Tuning' or via GPU-Z utility under the 'BIOS' section
    Affected if The system has any of the four affected Vega firmware variants and no driver update has been applied

A system is affected if it runs any AMD Radeon Software version below 23.7.1, or if it contains a Radeon RX Vega 56/64 or Radeon Pro Vega 56/64 GPU with an unpatched driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.q3 / 23.7.1 or later
Fixed in 23.q323.7.1
Interim mitigation

Apply AMD vendor-supplied graphics driver updates to patch the input validation vulnerability; organizations should inventory affected systems and deploy tested driver updates.

Recommended fix High confidence

Radeon Software 23.7.1 or later (or 23.q3 and later)

  1. 1. Visit the AMD support website (amd.com/support) to download the latest Radeon Software
  2. 2. Download Radeon Software version 23.7.1 or later (or version 23.q3 and later) for your specific GPU model
  3. 3. Run the downloaded installer and follow the prompts to update the AMD Radeon Graphics display driver
  4. 4. Restart your computer to complete the driver installation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Radeon Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-31320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data