CVE-2019-7246
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 issue was discovered in atillk64.sys in AMD ATI Diagnostics Hardware Abstraction Sys/Overclocking Utility 5.11.9.0. The vulnerable driver exposes a wrmsr instruction and does not properly filter the Model Specific Register (MSR). Allowing arbitrary MSR writes can lead to Ring-0 code execution and escalation of privileges.
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 confidenceThe atillk64.sys driver in AMD ATI Diagnostics Hardware Abstraction Sys/Overclocking Utility 5.11.9.0 exposes a wrmsr instruction without proper Model Specific Register (MSR) filtering. This allows a local attacker to write to arbitrary MSRs, achieving Ring-0 code execution and escalating privileges to kernel level.
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= 5.11.9.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate atillk64.sys driver fileSearch for atillk64.sys in system directories: C:\Windows\System32\drivers\ and C:\Windows\SysWOW64\drivers\, or use 'dir /s C:\atillk64.sys' from an elevated command promptAffected if The file atillk64.sys exists on the system
-
Check driver file versionRight-click the atillk64.sys file, select Properties, then view the Details tab for Product Version, or run 'wmic datafile where name="C:\\Windows\\System32\\drivers\\atillk64.sys" get Version' from elevated command promptAffected if The file version is 5.11.9.0 or if the file exists but version cannot be determined (assume vulnerable)
-
Verify driver is loadedRun 'sc query atillk64' or 'driverquery /v | findstr atillk64' from an elevated command prompt to check if the driver service is runningAffected if The driver service is present and running or in a started state
-
Check for AMD ATI Diagnostics utilitySearch for AMD ATI Diagnostics or Overclocking Utility in Add/Remove Programs (appwiz.cpl), or check Program Files for folders containing 'ATI' and 'Diagnostics' or 'Overclock' in the nameAffected if The AMD ATI Diagnostics/Overclocking Utility version 5.11.9.0 is installed
The system is affected if atillk64.sys driver version 5.11.9.0 is present on the system or if the AMD ATI Diagnostics/Overclocking Utility is installed, regardless of whether the driver is currently loaded.
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 dataRemove or disable the vulnerable AMD ATI Diagnostics/Overclocking utility and its atillk64.sys driver from affected systems, or apply any vendor-provided patch if available.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7246 — 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-7246 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