vmx86.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of vmx86.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 0/76 multi-engine detections. SHA256 a5834d6075e9d93f. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

vmx86.sys - Analysis Report

DriverShield analyzed the Windows kernel driver vmx86.sys and assigned a verdict of Vulnerable with a composite risk score of 72/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (72/100)
YARA matches2
Multi-engine detections0 / 76
File size100928 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-04-02
SHA256a5834d6075e9d93f3a3f58da9ca48d910100ebe7acdee6b23b0b8fed11cfebb8
SHA1a0df87a8e1e7af6663c048af03422de146749b8c
MD52fcca24c1e3c8a7cef3fe0065a85aeee

Driver identity

Version resource data embedded in the vmx86.sys PE header, as extracted by the analysis engine.

File descriptionVMware kernel driver
ProductVMware kernel driver
CompanyBroadcom Inc.
Original filenamevmx86.sys
Internal namevmx86.sys
File version25.0.0.0
CopyrightCopyright © 1998-2025 Broadcom.

How the 72/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface66 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (31)

Kernel-mode APIs resolved from the Import Address Table of vmx86.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ProbeForReadlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
SeAccessChecklowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 31 resolved.

IOCTL dispatch codes (22)

Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.

CodeSeverityTransferDescription
0x0034BBFFhighMETHOD_NEITHERFILE_DEVICE_DISK Function #3839
0x00808B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #738
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022BA00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3712
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00228349mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #210
0x0080B94EmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #3667
0x0034BF1EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #4039
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0080B589mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3426
0x00808310mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #196
0x00808611mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #388
0x00804F05mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #961
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x00228FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1018
0x002225E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2426
0x0022D7E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1530
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x0022341CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3335
0x00340314mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #197
0x00340035mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #13
0x9C40F6B4mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3501

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x10DE80x10E006.32CODE, EXEC, READ
.rdata0x18580x1A004.08IDATA, READ
.data0x90D80x0C000.54IDATA, READ, WRITE
.pdata0x16980x18004.5IDATA, READ
INIT0x0C720x0E004.9CODE, EXEC, READ, DISCARD
.rsrc0x03780x04002.96IDATA, READ, DISCARD
.reloc0x00300x02000.63IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (13)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial3300000125F31CB555767340D6000000000125
Valid from2025-02-20 20:08 UTC
Valid until2026-02-18 20:08 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 1.

Frequently asked questions about vmx86.sys

Is vmx86.sys safe?

Based on DriverShield static and dynamic analysis, vmx86.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 72/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of vmx86.sys?

vmx86.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: a5834d6075e9d93f3a3f58da9ca48d910100ebe7acdee6b23b0b8fed11cfebb8.

What is vmx86.sys?

vmx86.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact