LenovoDiagnosticsDriver.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of LenovoDiagnosticsDriver.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 1/75 multi-engine detections. SHA256 f05b1ee9e2f6ab70. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

LenovoDiagnosticsDriver.sys - Analysis Report

DriverShield analyzed the Windows kernel driver LenovoDiagnosticsDriver.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches3
Multi-engine detections1 / 75
File size40472 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-09-06
SHA256f05b1ee9e2f6ab704b8919d5071becbce6f9d0f9d0ba32a460c41d5272134abe
SHA1b89a8eef5aeae806af5ba212a8068845cafdab6f
MD5b941c8364308990ee4cc6eadf7214e0f

Driver identity

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

File descriptionLenovo Diagnostics Driver for Windows 10 and later.
ProductLenovo Diagnostics
CompanyLenovo Group Limited (R)
Original filenameLenovoDiagnosticsDriver.sys
Internal nameLenovoDiagnosticsDriver.sys
File version1.0.4.0
Copyright© 2021 Lenovo Group Limited. All rights reserved.

How the 78/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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface66 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (20)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (7)

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
0x00222000medium (known exploit)METHOD_BUFFEREDDriver communication init
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x003403ACmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #235
0x00340090mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #36

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x11B60x12006.15CODE, EXEC, READ
.rdata0x0E340x10003.93IDATA, READ
.data0x02800x04001.45IDATA, READ, WRITE
.pdata0x02DC0x04003.17IDATA, READ
PAGE0x1C8C0x1E006.08CODE, EXEC, READ
INIT0x056E0x06004.81CODE, EXEC, READ, DISCARD
.rsrc0x04980x06002.85IDATA, READ, DISCARD
.reloc0x00400x02000.83IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Lenovogrouplimitedr_Lenovodiagnosticsdriversys_Lenovodiagnostics_F05BmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - LenovoDiagnosticsDriver.sys. Investigate matches in context: expected filena...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about LenovoDiagnosticsDriver.sys

Is LenovoDiagnosticsDriver.sys safe?

Based on DriverShield static and dynamic analysis, LenovoDiagnosticsDriver.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of LenovoDiagnosticsDriver.sys?

LenovoDiagnosticsDriver.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: f05b1ee9e2f6ab704b8919d5071becbce6f9d0f9d0ba32a460c41d5272134abe.

What is LenovoDiagnosticsDriver.sys?

LenovoDiagnosticsDriver.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact