iaStorAVC.sys - Suspicious (40/100) - DriverShield Analysis

Analysis of iaStorAVC.sys: suspicious verdict, risk score 40/100. 2 YARA matches, 0/75 multi-engine detections. SHA256 a46a34e6dc1573d2. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

iaStorAVC.sys - Analysis Report

DriverShield analyzed the Windows kernel driver iaStorAVC.sys and assigned a verdict of Suspicious with a composite risk score of 40/100, indicating some risk signals warranting review (30-59 band).

Verdict	Suspicious (40/100)
YARA matches	2
Multi-engine detections	0 / 75
File size	885568 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-10-11
SHA256	a46a34e6dc1573d29b87ad22b336c6a7358a657a416b1643c0d3dad671d81692
SHA1	ad6be9c81e05628af93ff3ba070edcce381f8422
MD5	76b3dfb22c302dba9fa58c62d9668d04

Driver identity

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

File description	Intel(R) Rapid Storage Technology driver (inbox) - x64
Product	Intel(R) Rapid Storage Technology driver (inbox)
Company	Intel Corporation
Original filename	iaStorAVC.sys
Internal name	iaStorAVC.sys
File version	15.44.0.1015
Copyright	Copyright (C), Intel Corporation. All rights reserved.

How the 40/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	35 / 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 (18)

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

API	Risk	Why it matters
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
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineEx	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
KeInitializeEvent	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
DbgPrintEx	low	Standard kernel API - generally benign
ZwOpenKey	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
0x0080828B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #162
0x008087C7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #497
0x0080BB83	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3808
0x0080FFFF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #4095
0x0080B28B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3234
0x00346683	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #2464
0x0080918B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1122
0x0080888B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #546
0x0080838B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #226
0x00808B8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #738
0x00808A8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #674
0x00808F8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #994
0x0080878B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #482
0x0080820F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #131
0x0080B983	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3680
0x0080818B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #98
0x0080908B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1058
0x0080A183	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2144
0x0080898B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #610
0x0080E913	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2628
0x0022E8CB	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #2610
0x0080858B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #354
0x0080933B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1230
0x0022708B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3106

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	0xBFC83	0xBFE00	6.43	CODE, EXEC, READ
.rdata	0x7C14	0x7E00	5.38	IDATA, READ
.data	0x3CBE0	0x1C00	3.99	IDATA, READ, WRITE
.pdata	0x963C	0x9800	5.88	IDATA, READ
.gfids	0x0004	0x0200	0.02	IDATA, READ
PAGE	0x04FC	0x0600	5.41	CODE, EXEC, READ
INIT	0x0DC2	0x0E00	5.17	CODE, EXEC, READ, DISCARD
.rsrc	0x09F0	0x0A00	3.61	IDATA, READ, DISCARD
.reloc	0x09C8	0x0A00	5.4	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Enforced
Mitigation score	60 / 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.
• 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.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.
• Force Integrity - IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY is set - the OS validates the signature before loading.

YARA rule matches (2)

Rule	Severity	Detects
SUSP_PhysMem	high	Physical memory mapping
SUSP_Callbacks	medium	Kernel callback registration

MITRE ATT&CK techniques (16)

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
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
T1562.006	Indicator Blocking	Defense Evasion
T1564.001	Hidden Files and Directories	Defense Evasion
T1569.002	System Services: 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	330000045FF3C96C1A7FF7DA1D00000000045F
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 iaStorAVC.sys

Is iaStorAVC.sys safe?

Based on DriverShield static and dynamic analysis, iaStorAVC.sys shows some suspicious signals and warrants manual review. Its composite risk score is 40/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of iaStorAVC.sys?

iaStorAVC.sys has a DriverShield composite risk score of 40/100, placing it in the suspicious verdict band. SHA256: a46a34e6dc1573d29b87ad22b336c6a7358a657a416b1643c0d3dad671d81692.

What is iaStorAVC.sys?

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