winverbs.sys - Clean (16/100) - DriverShield Analysis

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

winverbs.sys - Analysis Report

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

VerdictClean (16/100)
YARA matches0
File size73016 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256d2a5ed039ed83010e0bb4bb1a69f9d142d42be2c75e56cfcf3f157a735cb688e
SHA14a764ebd55ec250b2bfe0733c010211229a7e28b
MD5f4c4fd42f8dd657157823db617cc3a3d

Driver identity

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

File descriptionKernel WinVerbs
ProductOpenFabrics Windows
CompanyMellanox
Original filenamewinverbs.sys
Internal namewinverbs.sys
File version5.50.14695
CopyrightCopyright© 2009 Mellanox Technologies Ltd

How the 16/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 imports30 / 100
IOCTL dispatch surface48 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (6)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign

IOCTL dispatch codes (16)

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
0x008083FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #255
0x0080BF83highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #4064
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x008000BBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #46
0x0022341BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3334
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080B315mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3269
0x0080AB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2757
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x002263E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2298
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0034EF15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3013
0x00340078mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #30
0x00340318mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #198
0x00340038mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #14

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xC55B0xC6006.13CODE, EXEC, READ
.rdata0x12FC0x14004.94IDATA, READ
.data0x0D980x02001.82IDATA, READ, WRITE
.pdata0x08340x0A003.89IDATA, READ
PAGE0x052C0x06005.49CODE, EXEC, READ
INIT0x04580x06004.1CODE, EXEC, READ, DISCARD
.rsrc0x03780x04003.01IDATA, READ, DISCARD
.reloc0x00500x02001.01IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
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
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 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 winverbs.sys

Is winverbs.sys safe?

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

What is the risk score of winverbs.sys?

winverbs.sys has a DriverShield composite risk score of 16/100, placing it in the clean verdict band. SHA256: d2a5ed039ed83010e0bb4bb1a69f9d142d42be2c75e56cfcf3f157a735cb688e.

What is winverbs.sys?

winverbs.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 · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact