silabser.sys - Clean (14/100) - DriverShield Analysis

Analysis of silabser.sys: clean verdict, risk score 14/100. 0 YARA matches, 0/75 multi-engine detections. SHA256 d1a4b2fa462dbdfe. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

silabser.sys - Analysis Report

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

VerdictClean (14/100)
YARA matches0
Multi-engine detections0 / 75
File size97160 bytes
Code-signing signerSilicon Laboratories Inc.
Analyzed2026-05-01
SHA256d1a4b2fa462dbdfed7e263df79e9f96f779eebc1026cd4d8e1c1bb31f48eeb69
SHA1f8359676e7797238a2325f7a45467b1c98a35119
MD50586bf25ce29189803e377610a15c4a5

Driver identity

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

File descriptionSilicon Labs CP210x USB to UART Bridge Driver (64-bit)
ProductSilicon Labs USBXpress Software
CompanySilicon Laboratories Inc.
Original filenamesilabser.sys
Internal namesilabser
File version6.7.6.2130
CopyrightCopyright © 2018 Silicon Laboratories Inc., All Rights Reserved.

How the 14/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 matches0 / 100
Dangerous kernel imports15 / 100
IOCTL dispatch surface54 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (5)

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

APIRiskWhy it matters
KeBugCheckExmediumModerate risk - system modification capability
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (18)

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
0x0080978BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1506
0x0080938BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1250
0x0080968BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1442
0xC350D1B7highMETHOD_NEITHERCUSTOM_MSI Function #1133
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00222008mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2050
0x0022208CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2083
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00808889mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #546
0x0080CB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #709
0x0080E70DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2499
0x0080430DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #195
0x0034472DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #459
0x0080007EmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #31
0x0022341EmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #3335
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x003403BCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #239

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xB1570xB2006.39CODE, EXEC, READ
.rdata0x10740x12004.77IDATA, READ
.data0x0FF40x02001.1IDATA, READ, WRITE
.pdata0x08B80x0A004.17IDATA, READ
PAGESRP00x31240x32006.17CODE, EXEC, READ
PAGE0x01210x02004.05CODE, EXEC, READ
PAGESER0x01F30x02005.97CODE, EXEC, READ
INIT0x06B40x08005.15CODE, EXEC, READ, DISCARD
.rsrc0x04200x06002.53IDATA, READ, DISCARD
.reloc0x00300x02000.6IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

MITRE ATT&CK techniques (6)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
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

SignerSilicon Laboratories Inc.
Signer organisationSilicon Laboratories Inc.
IssuerSymantec Class 3 SHA256 Code Signing CA
Serial4CDD2F3C085D4BA9675DB3D7397BEE33
Valid from2015-11-04 00:00 UTC
Valid until2018-11-03 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about silabser.sys

Is silabser.sys safe?

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

What is the risk score of silabser.sys?

silabser.sys has a DriverShield composite risk score of 14/100, placing it in the clean verdict band. SHA256: d1a4b2fa462dbdfed7e263df79e9f96f779eebc1026cd4d8e1c1bb31f48eeb69.

What is silabser.sys?

silabser.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Silicon Laboratories Inc..

Related: Other drivers signed by Silicon Laboratories Inc. · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact