dbcve.org
Ryzen MasterApplication · Amd

CVE-2023-20564

MEDIUM · 6.7 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 2.11.2.2659 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
Insufficient validation in the IOCTL (Input Output Control) input buffer in AMD Ryzen™ Master may permit a privileged attacker to perform memory reads/writes potentially leading to a loss of confidentiality or arbitrary kernel 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

This is a local privilege escalation vulnerability in AMD Ryzen Master where insufficient validation of IOCTL input buffers allows a privileged attacker to perform arbitrary memory reads/writes, potentially achieving kernel-mode code execution. The vulnerability requires the attacker to already have privileged access on the target system.

MitigationApply the vendor patch when available; until then, restrict access to AMD Ryzen Master and minimize the attack surface by ensuring only necessary personnel have privileged access.

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
Ryzen MasterApplication
Affected:< 2.11.2.2659
Ryzen Master Monitoring SdkApplication
Affected:< august_2023

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. Locate AMD Ryzen Master installation
    Check for Ryzen Master in typical installation paths: C:\Program Files\AMD\RyzenMaster\ or C:\Program Files (x86)\AMD\RyzenMaster\. Also search for 'RyzenMaster.exe' via file explorer or Get-ChildItem -Recurse command.
    Affected if The software is found installed on the system
  2. Identify installed version of Ryzen Master
    Right-click RyzenMaster.exe, select Properties, then look at the Details tab for Product Version. Alternatively, run: (Get-Item 'C:\Program Files\AMD\RyzenMaster\RyzenMaster.exe').VersionInfo.ProductVersion
    Affected if The version number is lower than 2.11.2.2659
  3. Check for Ryzen Master Monitoring SDK
    Search for files named 'AmdRyzenMasterDriver.sys' or check for the service 'AmdRyzenMasterDriver' via: Get-Service | Where-Object {$_.Name -like '*RyzenMaster*'}. Also look in C:\Windows\System32\drivers\ for the driver file.
    Affected if The driver/service is present and running
  4. Determine driver version if present
    If AmdRyzenMasterDriver.sys exists, right-click the file, select Properties, and check the Details tab for File Version or Product Version.
    Affected if The driver version is below the patched version (2.11.2.2659 or august_2023 for SDK)
  5. Verify service status
    Open Services (services.msc) and look for 'AMD Ryzen Master' or 'AmdRyzenMasterDriver' service. Check if it is Running or set to start automatically.
    Affected if The service is running or set to auto-start, indicating the vulnerable IOCTL interface is active

You are affected if AMD Ryzen Master or its driver is installed with a version prior to 2.11.2.2659 (or Monitoring SDK prior to august_2023) and the service/driver is active on the system.

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 2.11.2.2659 or later
Fixed in 2.11.2.2659
Interim mitigation

Apply the vendor patch when available; until then, restrict access to AMD Ryzen Master and minimize the attack surface by ensuring only necessary personnel have privileged access.

Recommended fix High confidence

Ryzen Master version 2.11.2.2659 or later; Ryzen Master Monitoring Sdk August 2023 release or later

  1. 1. Navigate to the official AMD website and locate the AMD Ryzen Master download page
  2. 2. Download AMD Ryzen Master version 2.11.2.2659 or later
  3. 3. If using Ryzen Master Monitoring SDK, download the August 2023 release or later version
  4. 4. Close any running instances of Ryzen Master
  5. 5. Uninstall the current version of Ryzen Master through Windows Control Panel > Programs and Features
  6. 6. Run the installer for the new version with administrator privileges
  7. 7. Follow the on-screen installation prompts to complete the upgrade
  8. 8. Restart the system after installation to ensure all services initialize correctly
Caveat Standard upgrade - review release notes for any changes to monitoring features or system requirements

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

Fix this in Ryzen Master Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20564 — 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-20564 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