108B.sys - Suspicious (38/100) - DriverShield Analysis

Analysis of 108B.sys: suspicious verdict, risk score 38/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 fe55e5dbae750e90. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

108B.sys - Analysis Report

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

Verdict	Suspicious (38/100)
YARA matches	0
Multi-engine detections	0 / 76
File size	3822496 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-04-24
SHA256	fe55e5dbae750e9021161fdaa634d6a6138d406e042e3976c01613cabe15a51f
SHA1	da4509c56b327e64aa080d64d028cdaf34a5afbd
MD5	a32d4fe15c45eb820716740dd51c142c

Driver identity

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

File description	C-MEDIA Inc. USB Audio Class 1.0 and 2.0 Device Driver
Product	C-MEDIA Inc. USB Audio Class 1.0 and 2.0 Device
Company	C-MEDIA Inc.
Original filename	108B.sys
Internal name	108B.sys
File version	10.0.0018.11573
Copyright	© C-Media Inc. All rights reserved.

How the 38/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	100 / 100
IOCTL dispatch surface	100 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	80 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (19)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
RtlInitUnicodeString	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign
ZwCreateFile	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
ExAllocatePool	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
ExFreePool	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
DbgPrint	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
0x00808C0F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #771
0x00808E0F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #899
0x0080840F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #259
0x00808B8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #738
0x00347A83	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3744
0x0080A0FF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2111
0x008080C7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #49
0x0080B38B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3298
0x0080838B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #226
0x00343883	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3616
0x00808F8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #994
0x0022F56B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3418
0x0080479F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #487
0x0022011B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #70
0x00226423	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #2312
0x008090FF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1087
0x00346683	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #2464
0x00806583	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2400
0x0080A383	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2272
0x008087C7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #497
0x0080AD8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2914
0x002283C3	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #240
0x0080B18B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3170
0x0080880F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #515

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	0x13CC32	0x13CE00	6.44	CODE, EXEC, READ
RT_CODE	0x079F	0x0800	5.45	CODE, EXEC, READ
.rdata	0x9F448	0x9F600	7.88	IDATA, READ
.data	0x184718	0x184600	7.04	IDATA, READ, WRITE
.pdata	0x70E0	0x7200	6.03	IDATA, READ
PAGE	0x37578	0x37600	6.39	CODE, EXEC, READ
INIT	0x0E30	0x1000	5.03	CODE, EXEC, READ, DISCARD
.rsrc	0x0AC0	0x0C00	3.3	IDATA, READ, DISCARD
.reloc	0x1614	0x1800	5.32	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	55 / 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.
• Packed Section: .rdata - Section has entropy 7.88 (threshold: 7.0), indicating possible packing or encrypted content.
• Packed Section: .data - Section has entropy 7.04 (threshold: 7.0), indicating possible packing or encrypted content.

MITRE ATT&CK techniques (10)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
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	System Services: Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows Hardware Compatibility Publisher
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Third Party Component CA 2012
Serial	330000006D9DA53E87009D334900000000006D
Valid from	2018-09-20 19:45 UTC
Valid until	2019-09-20 19:45 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Microsoft Windows Third Party Component CA 2012

Symbolic execution

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

Frequently asked questions about 108B.sys

Is 108B.sys safe?

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

What is the risk score of 108B.sys?

108B.sys has a DriverShield composite risk score of 38/100, placing it in the suspicious verdict band. SHA256: fe55e5dbae750e9021161fdaa634d6a6138d406e042e3976c01613cabe15a51f.

What is 108B.sys?

108B.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas

---

DriverShield © 2025-2026 · Terms · Privacy · Contact