vmmemctl.sys - Clean (22/100) - DriverShield Analysis

Analysis of vmmemctl.sys: clean verdict, risk score 22/100. 0 YARA matches. SHA256 27606e9ebc265633. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

vmmemctl.sys - Analysis Report

DriverShield analyzed the Windows kernel driver vmmemctl.sys and assigned a verdict of Clean with a composite risk score of 22/100, indicating no notable risk signals (0-29 band).

VerdictClean (22/100)
YARA matches0
File size42304 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-03-22
SHA25627606e9ebc2656331cd56bba1879e6a063ea9901b511fa0c5060b3e3941fe991
SHA15be7512fff7e9c41c3125e062344112401add575
MD575197e7ead8e0cd487cf1a76567907bd

Driver identity

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

File descriptionVMware server memory controller
ProductVMware server memory controller
CompanyVMware, Inc.
Original filenamevmmemctl.sys
Internal namevmmemctl.sys
File version7.5.5.0
CopyrightCopyright © 1998-2019 VMware, Inc.

How the 22/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 matches0 / 100
Dangerous kernel imports93 / 100
IOCTL dispatch surface12 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (15)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoCreateSymbolicLinklowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00808689mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #418
0x00340350mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #212
0x00340031mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #12

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x23C70x24006.34CODE, EXEC, READ
.rdata0x071C0x08003.96IDATA, READ
.data0x00200x02000.32IDATA, READ, WRITE
.pdata0x02100x04002.38IDATA, READ
INIT0x08400x0A005.13CODE, EXEC, READ, DISCARD
.rsrc0x03B00x04003.13IDATA, READ, DISCARD
.reloc0x00140x02000.24IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (9)

Techniques this driver could enable if loaded by an adversary.

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

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about vmmemctl.sys

Is vmmemctl.sys safe?

Based on DriverShield static and dynamic analysis, vmmemctl.sys is assessed as clean, with no notable risk signals. Its composite risk score is 22/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of vmmemctl.sys?

vmmemctl.sys has a DriverShield composite risk score of 22/100, placing it in the clean verdict band. SHA256: 27606e9ebc2656331cd56bba1879e6a063ea9901b511fa0c5060b3e3941fe991.

What is vmmemctl.sys?

vmmemctl.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact