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

Analysis of iaStorV.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 0/75 multi-engine detections. SHA256 7e862c0367b382ad. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

iaStorV.sys - Analysis Report

DriverShield analyzed the Windows kernel driver iaStorV.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).

Verdict	Vulnerable (72/100)
YARA matches	2
Multi-engine detections	0 / 75
File size	413088 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-10-11
SHA256	7e862c0367b382ade309dea6beb95fd2eed15cae8bdda37658d66484c00f88bb
SHA1	95dfc01672bb6667fc3ae4f9c1e349385f31b25f
MD5	061fa45f59c7328c4749b0e5baa9fc52

Driver identity

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

File description	Intel Matrix Storage Manager driver - x64
Product	Intel Matrix Storage Manager driver
Company	Intel Corporation
Original filename	iaStor.sys
Internal name	iaStor.sys
File version	8.6.2.1019
Copyright	Copyright(C) Intel Corporation 1994-2008

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.

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	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (25)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwCreateKey	medium	Moderate risk - system modification capability
IoGetDeviceObjectPointer	medium	Moderate risk - system modification capability
ZwQueryValueKey	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign

IOCTL dispatch codes (40)

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
0x0080BA0F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3715
0x0080BF83	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #4064
0x0080878B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #482
0x002283FF	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #255
0x0080828B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #162
0xC350418B	high	METHOD_NEITHER	CUSTOM_MSI Function #98
0x0080840F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #259
0x0080E9FF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2687
0x00808B8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #738
0x00808F8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #994
0x0080838B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #226
0x0080808B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #34
0x0022E8CB	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #2610
0x0080BB83	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3808
0x0080868B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #418
0x008003C3	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #240
0x00346183	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #2144
0x00346083	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #2080
0x00800C47	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #785
0x0080850F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #323
0x0080898B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #610
0x00808B03	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #704
0x00220113	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #68
0x0022340F	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3331

Showing 24 of 40 extracted control codes.

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	0x58907	0x58A00	6.3	CODE, EXEC, READ
.rdata	0x29CC	0x2A00	5.23	IDATA, READ
.data	0xB8380	0x1600	3.74	IDATA, READ, WRITE
.pdata	0x30E4	0x3200	5.6	IDATA, READ
INIT	0x1054	0x1200	4.97	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x0458	0x0600	2.61	IDATA, READ, DISCARD
.reloc	0x0F56	0x1000	1.87	IDATA, READ, DISCARD

Exploit mitigations

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

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
• No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

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 (13)

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
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
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
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Production PCA 2011
Serial	3300000460CF42A912315F6FB3000000000460
Valid from	2023-11-16 19:20 UTC
Valid until	2024-11-14 19:20 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Microsoft Windows Production PCA 2011

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 iaStorV.sys

Is iaStorV.sys safe?

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

iaStorV.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 7e862c0367b382ade309dea6beb95fd2eed15cae8bdda37658d66484c00f88bb.

What is iaStorV.sys?

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