kernel-driver.sys - Clean (25/100) - DriverShield Analysis

Analysis of kernel-driver.sys: clean verdict, risk score 25/100. 1 YARA match. SHA256 b602bdc9ec03888a. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

kernel-driver.sys - Analysis Report

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

Verdict	Clean (25/100)
YARA matches	1
File size	7168 bytes
Analyzed	2026-08-25
SHA256	b602bdc9ec03888aec5e0ee2e6905ddb547ad51b1bfac845d76461ce04118969
SHA1	8cb63280a1b8caeac95516b9408922632084bbb4
MD5	6eef995c744286700bc25bde292676df

How the 25/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	30 / 100
Dangerous kernel imports	99 / 100
IOCTL dispatch surface	6 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	50 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (6)

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

API	Risk	Why it matters
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessId	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ExAllocatePool2	low	Standard kernel API - generally benign
ProbeForWrite	low	Standard kernel API - generally benign
ProbeForRead	low	Standard kernel API - generally benign

IOCTL dispatch codes (2)

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
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x00342024	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #2057

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	0x0CA6	0x0E00	5.74	CODE, EXEC, READ
.rdata	0x034C	0x0400	3.65	IDATA, READ
.data	0x0020	0x0000	0	IDATA, READ, WRITE
.pdata	0x006C	0x0200	0.94	IDATA, READ
INIT	0x02D0	0x0400	3.68	IDATA, READ, WRITE, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	50 / 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.
Unsigned - The driver is not digitally signed. It requires test signing mode or a bootloader exploit to load on 64-bit Windows.

YARA rule matches (1)

Rule	Severity	Detects
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.001	Process Injection: DLL Injection	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1211	Exploitation for Defense Evasion	Defense Evasion
T1489	Service Stop	Impact
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1553.006	Code Signing Policy Modification	Defense Evasion
T1562.001	Impair Defenses: Disable/Modify Tools	Defense Evasion
T1652	Device Driver Discovery	Discovery

Symbolic execution

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

Frequently asked questions about kernel-driver.sys

Is kernel-driver.sys safe?

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

What is the risk score of kernel-driver.sys?

kernel-driver.sys has a DriverShield composite risk score of 25/100, placing it in the clean verdict band. SHA256: b602bdc9ec03888aec5e0ee2e6905ddb547ad51b1bfac845d76461ce04118969.

What is kernel-driver.sys?

kernel-driver.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.