win32k.sys - Clean (20/100) - DriverShield Analysis

Analysis of win32k.sys: clean verdict, risk score 20/100. 0 YARA matches, 0/75 multi-engine detections. SHA256 ef965f62f54f0113. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

win32k.sys - Analysis Report

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

VerdictClean (20/100)
YARA matches0
Multi-engine detections0 / 75
File size812504 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-08-22
SHA256ef965f62f54f0113921844cf43b3ea5ff236beb3bebec4dd8184337abe2dc209
SHA1bd7c4f35f6d50cd4c65ef3672546dc9b5257e786
MD5104881f8d11143048afe6d2527257799

Driver identity

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

File descriptionMulti-User Win32 Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamewin32k.sys
Internal namewin32k.sys
File version10.0.26100.9168 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 20/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 imports57 / 100
IOCTL dispatch surface75 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

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

APIRiskWhy it matters
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
PsGetCurrentProcesslowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
RtlZeroMemorylowStandard kernel API - generally benign
RtlCopyMemorylowStandard kernel API - generally benign
RtlMoveMemorylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (25)

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
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0022341FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00808B48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #722
0x00343DBCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3951
0x003487E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #506
0x0022B3E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3322
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00340074mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #29
0x0022F981mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3680
0x00802500mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2368
0x00223D00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3904
0x9C400200mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #128
0x00340398mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #230
0x0022F146mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #3153
0x002226FCmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2495
0x00220738mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #462
0x0022A74CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2515
0x00224760mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #472
0x00226774mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2525

Showing 24 of 25 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x6D8770x6E0005.62CODE, EXEC, READ
fothk0x10000x10000.03CODE, EXEC, READ
.rdata0xC6100xD0003.79IDATA, READ
.data0xDC200xB0004.88IDATA, READ, WRITE
.pdata0xE4240xF0005.5IDATA, READ
.idata0x45960x50004.63IDATA, READ
TABLERO0x46740x50004.05IDATA, READ
PAGE0x04DB0x10002.67CODE, EXEC, READ
.edata0x14B8B0x150005.77IDATA, READ
INIT0x05440x10002.77CODE, EXEC, READ, DISCARD
GFIDS0x22B80x30003.39IDATA, READ, DISCARD
.rsrc0x04000x10001.1IDATA, READ, DISCARD
.reloc0x7BA40x80006.08IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1055.001Process Injection: DLL InjectionDefense Evasion
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000059B7ABC51A19E71241800000000059B
Valid from2026-04-16 19:09 UTC
Valid until2026-10-17 19:09 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about win32k.sys

Is win32k.sys safe?

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

What is the risk score of win32k.sys?

win32k.sys has a DriverShield composite risk score of 20/100, placing it in the clean verdict band. SHA256: ef965f62f54f0113921844cf43b3ea5ff236beb3bebec4dd8184337abe2dc209.

What is win32k.sys?

win32k.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 · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact