usbohci.sys - Clean (9/100) - DriverShield Analysis

Analysis of usbohci.sys: clean verdict, risk score 9/100. 0 YARA matches. SHA256 6685acf6b2b2e4c7. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

usbohci.sys - Analysis Report

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

Verdict	Clean (9/100)
YARA matches	0
File size	30208 bytes
Analyzed	2026-03-22
SHA256	6685acf6b2b2e4c73d219e5b22b9a398f2d2bd7b08be0d3246aac2c505045307
SHA1	8e0db229da992e68dff7d5f7a68eb26ccf5315ad
MD5	f6b0b639e4f872a6e03deda93c939867

Driver identity

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

File description	OHCI USB Miniport Driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	USBOHCI.sys
Internal name	USBOHCI.sys
File version	10.0.19041.4474 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 9/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	0 / 100
Dangerous kernel imports	15 / 100
IOCTL dispatch surface	27 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	50 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (1)

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

API	Risk	Why it matters
ExAllocatePoolWithTag	low	Standard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x008088B7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #557
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080B841	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #3600
0x00803B15	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #3781
0x0080858D	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #355
0x008000E0	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #56
0x00220F05	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #961
0x0034039C	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #231
0x0034002E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #11

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	0x5569	0x5600	6.25	CODE, EXEC, READ
.rdata	0x0890	0x0A00	4.23	IDATA, READ
.data	0x04B8	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x03FC	0x0400	4.16	IDATA, READ
.idata	0x017A	0x0200	2.86	IDATA, READ
INIT	0x0072	0x0200	1.67	CODE, EXEC, READ, DISCARD
GFIDS	0x00D0	0x0200	1.68	IDATA, READ, DISCARD
.rsrc	0x0400	0x0400	3.41	IDATA, READ, DISCARD
.reloc	0x01D4	0x0200	5.23	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	80 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
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.
Unsigned - The driver is not digitally signed. It requires test signing mode or a bootloader exploit to load on 64-bit Windows.

MITRE ATT&CK techniques (5)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1553.006	Code Signing Policy Modification	Defense Evasion
T1652	Device Driver Discovery	Discovery

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

Is usbohci.sys safe?

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

What is the risk score of usbohci.sys?

usbohci.sys has a DriverShield composite risk score of 9/100, placing it in the clean verdict band. SHA256: 6685acf6b2b2e4c73d219e5b22b9a398f2d2bd7b08be0d3246aac2c505045307.

What is usbohci.sys?

usbohci.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.