dbcve.org
Atidxx64Application · Amd

CVE-2019-5183

CRITICAL · 9.0 CVSS v3.1 Published 2020-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
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
An exploitable type confusion vulnerability exists in AMD ATIDXX64.DLL driver, versions 26.20.13031.10003, 26.20.13031.15006 and 26.20.13031.18002. A specially crafted pixel shader can cause a type confusion issue, leading to potential code execution. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered from VMware guest, affecting VMware host.

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 · high confidence

A type confusion vulnerability exists in AMD's ATIDXX64.DLL graphics driver (versions 26.20.13031.10003, 26.20.13031.15006, and 26.20.13031.18002) where a specially crafted pixel shader can cause type confusion, potentially enabling code execution. This vulnerability can be triggered from a VMware guest virtual machine to achieve code execution on the VMware host system.

MitigationApply AMD's patched graphics driver updates to address the type confusion vulnerability, and review VMware configurations to limit or isolate GPU passthrough from untrusted guest VMs.

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
Atidxx64Application
Affected:= 26.20.13031.10003= 26.20.13031.15006= 26.20.13031.18002

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 ATIDXX64.DLL on the system
    Search for ATIDXX64.DLL in typical driver locations such as C:\Windows\System32\drivers\ and C:\Windows\System32\. Right-click the file, select Properties, and view the Version tab to obtain the file version.
    Affected if The DLL exists on the system and the version matches 26.20.13031.10003, 26.20.13031.15006, or 26.20.13031.18002 exactly.
  2. Check AMD driver version via Windows Device Manager
    Open Device Manager, expand Display adapters, right-click the AMD graphics device, select Properties, go to the Driver tab, and record the Driver Version.
    Affected if The displayed driver version matches one of the three affected versions: 26.20.13031.10003, 26.20.13031.15006, or 26.20.13031.18002.
  3. Verify VMware GPU passthrough configuration
    On the VMware host, open the VM's .vmx configuration file and search for settings such as pciPassthru0.present, pciPassthru0.msiEnabled, or similar PCIe passthrough device configurations.
    Affected if GPU passthrough is enabled and an AMD graphics device is passed through to a guest virtual machine.
  4. Identify running AMD driver processes
    Open Task Manager, go to the Details tab, look for processes associated with AMD graphics services such as atieclxx.exe or amddrvtop.exe. Use Process Explorer to locate loaded DLL modules and confirm ATIDXX64.DLL is loaded.
    Affected if ATIDXX64.DLL is loaded in memory and its version matches any of the three affected versions.

The system is affected if ATIDXX64.DLL version 26.20.13031.10003, 26.20.13031.15006, or 26.20.13031.18002 is installed and GPU passthrough to a VMware guest is enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply AMD's patched graphics driver updates to address the type confusion vulnerability, and review VMware configurations to limit or isolate GPU passthrough from untrusted guest VMs.

Fix this in Atidxx64 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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