nvmedisk.sys - Clean (25/100) - DriverShield Analysis

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

nvmedisk.sys - Analysis Report

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

VerdictClean (25/100)
YARA matches0
Multi-engine detections0 / 75
File size128400 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-04-01
SHA256c3ee7ff205c7cff73f095d983d6109c0e208c248c1f7e7053fbfaecfdd7ec23a
SHA1242e8a1bdc4209fee29baf28360e5d5d871d21f2
MD5d2f1b8a9c695b32ba9ee6349b2c626a7

Driver identity

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

File descriptionNvme Disk Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamenvmedisk.sys
Internal namenvmedisk.sys
File version10.0.26100.7019 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 25/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 imports99 / 100
IOCTL dispatch surface54 / 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 nvmedisk.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwCreateKeymediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (18)

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
0x00347E83highMETHOD_NEITHERFILE_DEVICE_DISK Function #4000
0x00227417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x00223413highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3332
0x0034011BhighMETHOD_NEITHERFILE_DEVICE_DISK Function #70
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080DB05mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1729
0x0080AD1CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2887
0x0022011EmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #71
0x0022641EmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2311
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0080E281mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2208
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00340394mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #229
0x00340031mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #12
0x00228024mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #9

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x63B70x70005.84CODE, EXEC, READ
fothk0x10000x10000.03CODE, EXEC, READ
.rdata0x14F80x20003.29IDATA, READ
.data0x025C0x10000.15IDATA, READ, WRITE
.pdata0x06780x10002.22IDATA, READ
.idata0x13480x20003.1IDATA, READ
PAGE0x47370x50005.77CODE, EXEC, READ
INIT0x043B0x10002.24CODE, EXEC, READ, DISCARD
GFIDS0x00840x10000.19IDATA, READ, DISCARD
.rsrc0x55780x60003.47IDATA, READ, DISCARD
.reloc0x07600x10002.95IDATA, 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
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000518418419ADCBAD294F000000000518
Valid from2025-06-19 18:11 UTC
Valid until2026-06-17 18:11 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about nvmedisk.sys

Is nvmedisk.sys safe?

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

What is the risk score of nvmedisk.sys?

nvmedisk.sys has a DriverShield composite risk score of 25/100, placing it in the clean verdict band. SHA256: c3ee7ff205c7cff73f095d983d6109c0e208c248c1f7e7053fbfaecfdd7ec23a.

What is nvmedisk.sys?

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