WinRing0x64.sys - Malicious (88/100) - DriverShield Analysis

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

WinRing0x64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver WinRing0x64.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

Verdict	Malicious (88/100)
YARA matches	2
Multi-engine detections	0 / 76
File size	35968 bytes
Code-signing signer	WDKTestCert maple,133497572276910320
Analyzed	2026-08-02
SHA256	c30ebd80d2a1c5c15f0b706ed01c354730a9e2264b739d0d2d66ccb262c95f80
SHA1	79de839237aaf6ec7d8579dad1a6ce5d9abb9a43
MD5	70fc73bd536e951ce3f3bb99684b3088

How the 88/100 score breaks down

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

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	80 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	100 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	0 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	40 / 100

Kernel imports (21)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointer	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
ZwCreateKey	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
IoCreateDevice	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
DbgPrintEx	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
IoCreateDeviceSecure	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign

IOCTL dispatch codes (14)

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.

Code	Severity	Transfer	Description
0x9C402088	critical (known exploit)	METHOD_BUFFERED	MSR write (LnvMSRIO)
0x9C406104	high (known exploit)	METHOD_BUFFERED	Physical memory read (LnvMSRIO)
0x9C402084	high (known exploit)	METHOD_BUFFERED	MSR read (LnvMSRIO)
0x0080830F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #195
0x00343D07	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3905
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0034F045	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #3089
0x00808389	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #226
0x9C40A108	medium	METHOD_BUFFERED	CUSTOM_LENOVO Function #2114
0x9C40A148	medium	METHOD_BUFFERED	CUSTOM_LENOVO Function #2130
0x00343B05	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #3777
0x00340030	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #12
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x008024B4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2349

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x1544	0x1600	6.08	CODE, EXEC, READ
.rdata	0x103C	0x1200	4.39	IDATA, READ
.data	0x04F8	0x0400	1.39	IDATA, READ, WRITE
.pdata	0x02E8	0x0400	3.24	IDATA, READ
PAGE	0x1D0B	0x1E00	6.13	CODE, EXEC, READ
INIT	0x0632	0x0800	4.18	CODE, EXEC, READ, DISCARD
.reloc	0x0044	0x0200	0.89	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	100 / 100

• CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
• ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
• DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
• Valid Signature - The driver has a valid, non-expired digital signature.

YARA rule matches (2)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (15)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003	OS Credential Dumping	Credential Access
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1006	Direct Volume Access	Defense Evasion
T1014	Rootkit	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1542.001	Pre-OS Boot: System Firmware	Persistence
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1601	Modify System Image	Defense Evasion
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	WDKTestCert maple,133497572276910320
Issuer	WDKTestCert maple,133497572276910320
Serial	68C635612D4BB4B5414AF319D2C8EDD8
Valid from	2024-01-15 01:53 UTC
Valid until	2034-01-15 00:00 UTC
Signature validity	Verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7

Associated CVEs

• CVE-2020-14979 - WinRing0 - arbitrary MSR/physical memory access

Symbolic execution

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

Frequently asked questions about WinRing0x64.sys

Is WinRing0x64.sys safe?

Based on DriverShield static and dynamic analysis, WinRing0x64.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of WinRing0x64.sys?

WinRing0x64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: c30ebd80d2a1c5c15f0b706ed01c354730a9e2264b739d0d2d66ccb262c95f80.

What is WinRing0x64.sys?

WinRing0x64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by WDKTestCert maple,133497572276910320.

Related: Other drivers signed by WDKTestCert maple,133497572276910320 · CVE-2020-14979 · 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