LHA.sys - Vulnerable (72/100) - DriverShield Analysis

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

LHA.sys - Analysis Report

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

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections3 / 75
File size35520 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA256e75714f8e0ff45605f6fc7689a1a89c7dcd34aab66c6131c63fefaca584539cf
SHA1fcd615df88645d1f57ff5702bd6758b77efea6d0
MD5748cf64b95ca83abc35762ad2c25458f

Driver identity

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

File descriptionLHA
ProductMicrosoft® Windows® Operating System
CompanyLG Electronics Inc.
Original filenameLHA.sys
Internal nameLHA.sys
File version6.1.7600.16385 built by: WinDDK
Copyright[email protected]

How the 72/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 surface33 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 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 LHA.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
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (11)

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
0x008000FBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #62
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x9C402FB0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3052
0x9C403390mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3300
0x9C403394mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3301
0x9C403520mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3400
0x9C403638mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3470
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0034031CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #199

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x275E0x28006.31CODE, EXEC, READ
.rdata0x079C0x08004.2IDATA, READ
.data0x03810x04001.28IDATA, READ, WRITE
.pdata0x02B80x04003.13IDATA, READ
PAGE0x1A470x1C006.03CODE, EXEC, READ
INIT0x07280x08004.81CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03800x04003.07IDATA, READ, DISCARD
.reloc0x00600x02000.32IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Lgelectronicsinc_Lhasys_Microsoftwindowsoperatingsystem_23BAmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - LHA.sys. Investigate matches in context: expected filenames or standard vend...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (13)

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
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial33000000253A2738690A3451C1000000000025
Valid from2018-09-06 21:30 UTC
Valid until2019-09-06 21:30 UTC (expired)
Signature validityNot verified

Symbolic execution

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

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

Is LHA.sys safe?

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

What is the risk score of LHA.sys?

LHA.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: e75714f8e0ff45605f6fc7689a1a89c7dcd34aab66c6131c63fefaca584539cf.

What is LHA.sys?

LHA.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · 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