Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local code execution
-
DeliveryOpen handle to mtdispkm64.sys device
-
ExploitSend crafted IOCTL to sub_140006F0C
-
ExecutionTrigger improper privilege management in kernel
-
ImpactEscalate to SYSTEM/kernel privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires local access with the ability to run code as at least a low-privileged user on a Windows host that has the Moore Threads MTT S80 Driver Package 340.150 installed (the vulnerable mtdispkm64.sys kernel driver must be present and its IOCTL device reachable). Exploitation is limited by: no remote/network vector (AV:L - attacker must already have a foothold on the machine), the niche prerequisite of this specific Chinese GPU driver being installed, and the absence of any public exploit code. No user interaction is needed and only low privileges are required, so once local access exists the bar to escalate is low. No vendor patch is available, so mitigation is limited to removing/updating the driver or restricting local access. |
| Impact | This is a local privilege-escalation flaw (CWE-269 improper privilege management) in the Moore Threads MTT S80 GPU kernel driver mtdispkm64.sys, reachable via an unvalidated IOCTL handler (sub_140006F0C). The only CVSS provided is a vendor/VulDB CVSS 4.0 base of 9.3 (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H). The core primitives are credible: local vector, low complexity, low privileges, no user interaction, high impact on the local system. However, the score is inflated by rating the subsequent-system metrics SC:H/SI:H/SA:H - for a self-contained local kernel EoP there is no separate downstream system being compromised, so those should be N; dropping them yields a realistic CVSS 3.1 near 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, High). Cross-referencing exploitation signals: there is NO EPSS score, the CVE is NOT in CISA KEV, and NO public exploit or PoC is referenced (all four references are VulDB self-links). Per an SSVC-style read, exploitation is 'none' (no public exploit identified), the local-only vector makes it NOT automatable (no network-scannable mass exploitation), while technical impact is 'total' on the compromised host. Net: a genuine local EoP worth patching on affected hosts, but not an emergency mass-exploitation priority - the headline 9.3 overstates real-world urgency, and the absence of any vendor response means no fix currently exists, which is the more actionable concern than the score itself. |
| Exploit ScenarioDerived | A low-privileged user or malware already running on a Windows machine that has the Moore Threads MTT S80 driver installed sends a crafted IOCTL to mtdispkm64.sys, triggering the improper privilege-management flaw in sub_140006F0C to elevate to SYSTEM. This is a classic local EoP used as a second stage after initial access (phishing, commodity malware). No public PoC or exploit code is referenced at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 21, 2026
Local privilege escalation in the Moore Threads MTT S80 Driver Package 340.150 allows a low-privileged local user to abuse an improperly secured IOCTL handler and gain high-impact control over the system. The flaw resides in the Windows kernel-mode driver mtdispkm64.sys, specifically function sub_140006F0C, and is classified as CWE-269 improper privilege management; successful abuse yields high confidentiality, integrity and availability impact on both the vulnerable component and the subsequently compromised host. Exploitation requires an existing local foothold on a Windows machine with this specific GPU driver installed, with low privileges and no user interaction needed (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; vendor-published CVSS 4.0 score 9.3). No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but the low attack complexity and the absence of a vendor patch make the flaw attractive to local attackers already present on a host.
RemediationAI
No vendor-released patch was identified at time of analysis: Moore Threads was contacted early about the disclosure and did not respond, so there is no confirmed fixed version of the MTT S80 Driver Package to upgrade to - check the Moore Threads download/support channel (and the VulDB advisory at https://vuldb.com/vuln/408151) for a later driver release and treat any post-340.150 build as unverified until confirmed. Where the GPU is not required, the most reliable mitigation is to uninstall the MTT S80 driver package (or roll the machine back to a GPU/vendor driver that is not affected), accepting the loss of MTT S80 functionality; if the card must stay in service, compensate by hardening the local attack surface rather than expecting a fix. Restrict who may log on locally or run code on affected hosts (remove unnecessary local accounts, apply least-privilege and RDP/console access controls), since exploitation requires an existing low-privileged local foothold - this does not stop an attacker who already has a user shell. Use Windows Defender Application Control or AppLocker to block loading of mtdispkm64.sys on hosts that do not need it, at the cost of disabling the device driver, and monitor/alert on local attempts to open and issue IOCTLs to the driver's device interface; note that disabling a boot/display kernel driver may degrade or break graphics output, so test before broad deployment. Because a future patched driver could still be superseded, track the CVE record at https://vuldb.com/cve/CVE-2026-94425 for updated remediation guidance and re-enable the driver only after a vendor fix is confirmed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected technology is a Windows kernel-mode driver (mtdispkm64.sys) shipped with the Moore Threads MTT S80 GPU driver package, a Chinese domestic graphics card solution. The vulnerable element is the IOCTL dispatch routine sub_140006F0C, which processes user-supplied IOCTL requests from user mode into the kernel driver. Because the handler fails to properly validate or restrict the privileged operations it exposes, a caller holding only low privileges can cause the driver to perform actions on its behalf - the classic CWE-269 improper privilege management pattern where a privileged component grants capabilities beyond what the caller's token should permit. Kernel drivers execute at ring 0, so any authorization gap in an IOCTL interface effectively becomes a path from a standard user token to SYSTEM/kernel-level execution, matching the assessed impacts of high confidentiality, integrity and availability loss (and the CVSS 4.0 vector showing high impact on both the vulnerable system and subsequent systems). The CPE cpe:2.3:a:moore_threads:mtt_s80_driver_package:*:*:*:*:*:*:*:* does not constrain a fixed patch version, consistent with the vendor never publishing a fix.
Know when Mtt S80 Driver Package gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Local IOCTL reachable by any low-priv user (AV:L/PR:L/AC:L/UI:N); kernel EoP grants full host compromise (C/I/A:H) but stays on one system, so S:U.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
Articles & Coverage 1
Technical POC Analysis
The defect is CWE-269 Improper Privilege Management in the Windows kernel-mode display driver mtdispkm64.sys, part of Moore Threads MTT S80 Driver Package 340.150.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Moore Threads MTT S80 Driver Package 340.150 introduces a critical local privilege-escalation exposure on Windows systems equipped with that GPU driver, allowing an already-present low-privileged user or malware to gain high-impact control over the host. Because the affected component is a kernel-mode driver and no vendor-released patch identified at time of analysis, leadership should prioritize identifying and isolating affected endpoints, especially those used by privileged staff or in sensitive environments. Although no public exploit identified at time of analysis, the low attack complexity and lack of remediation raise the residual risk for any organization with this specific driver deployed.
No vendor-released patch identified at time of analysis. Interim mitigations include inventorying and isolating affected Windows systems with Moore Threads MTT S80 Driver Package 340.150, uninstalling or disabling the mtdispkm64.sys driver where the GPU is not required, enforcing least privilege to limit local footholds, restricting interactive logon for non-essential users, applying application allowlisting and EDR kernel-level monitoring, and monitoring vendor advisories for a fixed driver release.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-84244
GHSA-x62r-p8c2-p53f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB