mvumis.sys - Clean (7/100) - DriverShield Analysis

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

mvumis.sys - Analysis Report

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

Verdict	Clean (7/100)
YARA matches	0
File size	63800 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	69fbb0692c37da498014cc6cdc609e612a3207a17b280ede5c02248571f91f11
SHA1	af40ad74b1bd67e3cbfc4ccdad8f8367ab1237af
MD5	82b656712713424a707f1e127c68e02f

Driver identity

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

File description	Marvell Flash Controller Driver
Product	Marvell Flash Controller
Company	Marvell Semiconductor, Inc.
Original filename	speedyst.sys
Internal name	speedyst.sys
File version	1.0.5.1016 (PART_L3.131021-1012)
Copyright	Copyright (c) Marvell Semiconductor, Inc.

How the 7/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	0 / 100
IOCTL dispatch surface	24 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 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 mvumis.sys, ranked by exploitation relevance.

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

IOCTL dispatch codes (8)

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
0x0080888B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #546
0x0080908B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1058
0x00343417	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3333
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080C481	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #288
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x00340025	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #9
0x00340390	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #228

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	0x4C03	0x4E00	6.35	CODE, EXEC, READ
.rdata	0x04D4	0x0600	3.36	IDATA, READ
.data	0x0DC4	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x0258	0x0400	2.68	IDATA, READ
INIT	0x0370	0x0400	4.31	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x73E0	0x7400	3.6	IDATA, READ, DISCARD
.reloc	0x0010	0x0200	0.14	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.

MITRE ATT&CK techniques (3)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Production PCA 2011
Serial	330000023241FB59996DCC4DFF000000000232
Valid from	2019-05-02 21:24 UTC
Valid until	2020-05-02 21:24 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Microsoft Windows Production PCA 2011

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

Is mvumis.sys safe?

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

What is the risk score of mvumis.sys?

mvumis.sys has a DriverShield composite risk score of 7/100, placing it in the clean verdict band. SHA256: 69fbb0692c37da498014cc6cdc609e612a3207a17b280ede5c02248571f91f11.

What is mvumis.sys?

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