CVE-2019-5147
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 · uneditedAn exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13003.1007. A specially crafted pixel shader can cause a denial of service. 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 confidenceAn out-of-bounds read vulnerability exists in AMD's ATIDXX64.DLL graphics driver (version 26.20.13003.1007). A specially crafted malicious pixel shader can trigger the vulnerability, causing a denial of service. Notably, this can be exploited from within a VMware guest virtual machine to affect the host system, representing a VM escape scenario.
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= 26.20.13003.1007CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Locate ATIDXX64.DLL on the systemSearch for ATIDXX64.DLL in C:\Windows\System32\ (64-bit) or C:\Windows\SysWOW64\ (32-bit on 64-bit OS), or use PowerShell: Get-ChildItem -Path C:\Windows -Recurse -Filter ATIDXX64.DLL -ErrorAction SilentlyContinueAffected if The DLL file exists on the system at any location
-
Verify the exact file version of ATIDXX64.DLLRight-click the DLL file, select Properties, go to the Details tab, and check the File Version field; alternatively use PowerShell: (Get-Item 'C:\Windows\System32\ATIDXX64.DLL').VersionInfo.FileVersionAffected if File version equals exactly 26.20.13003.1007
-
Confirm AMD graphics driver is installed and activeOpen Device Manager, expand 'Display adapters', and check if an AMD GPU is listed with the Atidxx64 driver; alternatively check registry: HKLM\SYSTEM\CurrentControlSet\Services\Atidxx64Affected if AMD graphics driver with Atidxx64 component is installed and loaded
-
Determine if running as a VMware guest virtual machineCheck system information for VMware artifacts, look for VMware tools process (vmtoolsd.exe), or check for VM-specific BIOS identifiers using msinfo32Affected if The system is a VMware guest VM with the vulnerable DLL present (this enables the VM escape attack vector)
A user is affected if ATIDXX64.DLL exists on their system with exactly version 26.20.13003.1007 and the AMD graphics driver is actively loaded, particularly critical in VMware virtual machine environments where this can be exploited for VM escape.
Generated from the published advisory. Verify against your own configuration.
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 dataApply AMD's patched graphics driver update. For virtualized environments, ensure VMware tools are current and consider implementing microsegmentation or additional VM isolation controls as defense-in-depth measures.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-5147 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5147 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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