dbcve.org
Radeon Rx Vega M FirmwareOperating system · Intel

CVE-2023-20568

MEDIUM · 6.7 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 23.q3 / 23.7.1 or later.
See remediation →
69/100
Remediation priority · Elevated
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 signature verification of RadeonTM RX Vega M Graphics driver for Windows may allow an attacker with admin privileges to launch RadeonInstaller.exe without validating the file signature potentially leading to arbitrary code execution.

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 digital signature verification in the Radeon RX Vega M Graphics driver installer for Windows allows an attacker with administrative privileges to bypass code signing validation on RadeonInstaller.exe, potentially enabling execution of unsigned or malicious code disguised as a legitimate driver package.

MitigationApply the vendor-provided patch from AMD that addresses the signature verification vulnerability; organizations should also implement code signing verification policies and restrict administrative privileges where possible to limit exposure.

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 Rx Vega M FirmwareOperating system
Affected:< 23.10.01.46
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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 Radeon Software version
    Open Windows Settings > Apps > Apps & features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Radeon*'} | Select-Object Name, Version. Alternatively check Program Files/AMD for the installation directory and look for version info in the driver metadata.
    Affected if The installed AMD Radeon Software version is earlier than 23.7.1 or earlier than 23.q3 (e.g., 23.5.x, 23.4.x, etc.)
  2. Identify Intel Radeon Rx Vega M Graphics driver version
    Open Device Manager > Display adapters > Intel(R) UHD Graphics 630 (or similar Vega M variant) > Right-click > Properties > Driver tab. Note the driver version and date.
    Affected if The driver version for Intel Radeon Rx Vega M Graphics is earlier than 23.10.01.46, or the driver date is prior to the patched release.
  3. Check for presence of Vega 56/64 or Pro Vega graphics hardware
    Open Device Manager > Display adapters. Look for entries such as 'AMD Radeon Rx Vega 56', 'AMD Radeon Rx Vega 64', 'AMD Radeon Pro Vega 56', or 'AMD Radeon Pro Vega 64'. Alternatively, use PowerShell: Get-WmiObject -Class Win32_VideoController | Select-Object Name
    Affected if Any of these specific AMD Vega graphics cards (Vega 56, Vega 64, Pro Vega 56, Pro Vega 64) are listed as installed hardware.
  4. Locate RadeonInstaller.exe component
    Search for RadeonInstaller.exe on the system: use PowerShell: Get-ChildItem -Path C:\ -Filter RadeonInstaller.exe -Recurse -ErrorAction SilentlyContinue, or check typical AMD driver installation directories under Program Files.
    Affected if RadeonInstaller.exe is present on the system and corresponds to an unpatched AMD Radeon Software installation.

A user is affected if they have AMD Radeon Software version < 23.7.1 or < 23.q3, OR Intel Radeon Rx Vega M driver < 23.10.01.46, OR any of the Vega 56/64/Pro Vega graphics hardware installed with their associated drivers.

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 / 23.10.01.46 or later
Fixed in 23.q323.7.123.10.01.46
Interim mitigation

Apply the vendor-provided patch from AMD that addresses the signature verification vulnerability; organizations should also implement code signing verification policies and restrict administrative privileges where possible to limit exposure.

Recommended fix Moderate confidence

Radeon Software 23.7.1 or later / Vega M Firmware 23.10.01.46 or later (other Vega variants - contact AMD for patched driver availability)

  1. 1. Identify the specific AMD Radeon product in use (e.g., RX Vega M, RX Vega 56, RX Vega 64, or Pro Vega variants)
  2. 2. For RX Vega M: Navigate to AMD's official support page and download Radeon Software version 23.7.1 or later, or firmware version 23.10.01.46 or later
  3. 3. For RX Vega 56/64 and Pro Vega variants: Contact AMD support to verify if a patched driver/firmware is available, as these are listed as 'all versions' affected with no specific fixed version provided in the CVE details
  4. 4. Ensure you have administrator privileges on the system
  5. 5. Uninstall the current AMD Radeon software and drivers completely
  6. 6. Run the downloaded installer as Administrator
  7. 7. Verify the file signature of RadeonInstaller.exe before execution by right-clicking the file, selecting Properties, and checking the Digital Signatures tab
  8. 8. Restart the system after installation completes
Caveat Review release notes for driver version 23.7.1+ for any compatibility changes with specific games or applications

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

Fix this in Radeon Rx Vega M Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-20568 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