mssmbios.sys - Clean (21/100) - DriverShield Analysis

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

mssmbios.sys - Analysis Report

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

VerdictClean (21/100)
YARA matches0
Multi-engine detections0 / 75
File size79152 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-10-11
SHA256b158d81780504ab412c17bb9db0c710f6ad9c7f2b75e7095c2fc2fc1847dc9a0
SHA17ce0caea8cb2e7f02774f5d8d20ff1c45dc3c9f5
MD5fbe7841da9237bbf30ff6abd65984de7

Driver identity

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

File descriptionSystem Management BIOS Driver
ProductBaseBoardVersion
CompanyMicrosoft Corporation
Original filenamesmbios.sys
Internal namesmbios.sys
File version10.0.26100.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (12)

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

APIRiskWhy it matters
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (10)

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
0x9C403FFFhighMETHOD_NEITHERCUSTOM_LENOVO Function #4095
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080BF15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4037
0x0022E3E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2298
0x0080BA21mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3720
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00227428mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3338
0x00227400mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3328
0x00808D89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #866
0x00340398mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #230

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3F770x40006.13CODE, EXEC, READ
fothk0x10000x10000.02CODE, EXEC, READ
.rdata0x13640x20002.98IDATA, READ
.data0x07000x10000.46IDATA, READ, WRITE
.pdata0x05580x10001.77IDATA, READ
.idata0x088A0x10002.81IDATA, READ
PAGE0x17F20x20005.09CODE, EXEC, READ
INIT0x020D0x10001.21CODE, EXEC, READ, DISCARD
GFIDS0x00540x10000.12IDATA, READ, DISCARD
.rsrc0x07B80x10003.19IDATA, READ, DISCARD
.reloc0x05000x10002.09IDATA, 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.002System Services: Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000460CF42A912315F6FB3000000000460
Valid from2023-11-16 19:20 UTC
Valid until2024-11-14 19:20 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about mssmbios.sys

Is mssmbios.sys safe?

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

What is the risk score of mssmbios.sys?

mssmbios.sys has a DriverShield composite risk score of 21/100, placing it in the clean verdict band. SHA256: b158d81780504ab412c17bb9db0c710f6ad9c7f2b75e7095c2fc2fc1847dc9a0.

What is mssmbios.sys?

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