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

Analysis of winhv.sys: vulnerable verdict, risk score 72/100. 1 YARA match. SHA256 1abe49124bb18500. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

winhv.sys - Analysis Report

DriverShield analyzed the Windows kernel driver winhv.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 matches1
File size42504 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2561abe49124bb185009368f0b8cd4c0c5b57802987580140de6dc826dee9de34ef
SHA1f0cb12aab46ec80e1a60fbf8acc6ebb954f7b2c4
MD51588d61cf74fe332ac1a2080604b3db4

Driver identity

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

File descriptionWindows Hypervisor Interface Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameWinHv.sys
Internal nameWinHv.sys
File version10.0.19041.5072 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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 matches30 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface84 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (6)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetSystemInformationhighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign

IOCTL dispatch codes (13)

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
0x00222000medium (known exploit)METHOD_BUFFEREDDriver communication init
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0022F981mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3680
0x00802500mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2368
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00223DC0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3952
0x00222002mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2048
0x0034A002mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #2048
0x003403A8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #234

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x36090x38005.95CODE, EXEC, READ
.rdata0x0C180x0E004.11IDATA, READ
.data0x50000x02000.28IDATA, READ, WRITE
.pdata0x07500x08004.11IDATA, READ
.idata0x09DE0x0A004.7IDATA, READ
PAGE0x083A0x0A005.31CODE, EXEC, READ
.edata0x034E0x04004.55IDATA, READ
INIT0x06630x08005.22CODE, EXEC, READ, DISCARD
GFIDS0x00C40x02001.61IDATA, READ, DISCARD
.rsrc0x04100x06002.5IDATA, READ, DISCARD
.reloc0x02980x04003.75IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (8)

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
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000045FF3C96C1A7FF7DA1D00000000045F
Valid from2023-11-16 19:20 UTC
Valid until2024-11-14 19:20 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 winhv.sys

Is winhv.sys safe?

Based on DriverShield static and dynamic analysis, winhv.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 winhv.sys?

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

What is winhv.sys?

winhv.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.

Related: Other drivers signed by Microsoft Windows · 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