pciidex.sys - Clean (29/100) - DriverShield Analysis

Analysis of pciidex.sys: clean verdict, risk score 29/100. 1 YARA match. SHA256 8a96556a9b1965eb. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

pciidex.sys - Analysis Report

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

VerdictClean (29/100)
YARA matches1
File size57832 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2568a96556a9b1965ebfe58739ff2e3212540fa50d247b4a6612c4b18395ecb23b6
SHA16da25f69c41d9fcfee609831c83a7beb047c93c9
MD5315f8775d2f5096251e0c186e240c994

Driver identity

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

File descriptionPCI IDE Bus Driver Extension
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamepciidex.sys
Internal namepciidex.sys
File version10.0.19041.3636 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 29/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 surface18 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (15)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwCreateKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
KeSetEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (6)

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
0x0080BAFFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3775
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x003403A4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #233

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x31A90x32005.91CODE, EXEC, READ
.rdata0x0CB80x0E004.48IDATA, READ
.data0x03E80x02000.8IDATA, READ, WRITE
.pdata0x093C0x0A004.08IDATA, READ
.idata0x0C6A0x0E004.27IDATA, READ
PAGE0x41B40x42006.16CODE, EXEC, READ
.edata0x08F90x0A004.83IDATA, READ
INIT0x00820x02001.81CODE, EXEC, READ, DISCARD
GFIDS0x029C0x04002.54IDATA, READ, DISCARD
.rsrc0x04080x06002.48IDATA, READ, DISCARD
.reloc0x04A00x06004.61IDATA, 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 (9)

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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000041331BC198807A90774000000000413
Valid from2023-02-03 00:05 UTC
Valid until2024-02-01 00:05 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about pciidex.sys

Is pciidex.sys safe?

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

What is the risk score of pciidex.sys?

pciidex.sys has a DriverShield composite risk score of 29/100, placing it in the clean verdict band. SHA256: 8a96556a9b1965ebfe58739ff2e3212540fa50d247b4a6612c4b18395ecb23b6.

What is pciidex.sys?

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