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

Analysis of klhk.sys: vulnerable verdict, risk score 78/100. 2 YARA matches, 0/75 multi-engine detections. SHA256 5df42349faefcfd9. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

klhk.sys - Analysis Report

DriverShield analyzed the Windows kernel driver klhk.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 matches2
Multi-engine detections0 / 75
File size1277704 bytes
Code-signing signerKaspersky Lab
Analyzed2026-09-06
SHA2565df42349faefcfd9d577026268e17826c165963d073b34a867f5bc1abd0d5104
SHA1aa8905e41fee2d6dbe168d0f37f44364b08527f5
MD5f219d3951e3fbbeff1fbe5d5ca5cd6f8

Driver identity

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

File descriptionklhk [fre_win7_x64]
ProductCoretech Delivery
CompanyAO Kaspersky Lab
Internal nameklhk
File version20.5.3.0
Copyright© 2020 AO Kaspersky Lab. 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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (34)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
NtTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 34 resolved.

IOCTL dispatch codes (40)

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
0x00808F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #994
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x0080883BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #526
0x0022E8D3highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2612
0x00220117highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #69
0x0022641FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2311
0x00227473highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3356
0x00226563highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2392
0x00226567highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2393
0x0022736FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3291
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x00227F05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #4033
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x00229FE9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2042
0x0022BBE9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3834
0x0022DFE9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2042
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00808111mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #68
0x00808539mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #334
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00808289mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #162
0x00808801mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #512

Showing 24 of 40 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x322B60x324006.3CODE, EXEC, READ
bss0x80000x00000READ, WRITE
.rdata0x110FC0x112003.79IDATA, READ
.data0xA52600x81A004.37IDATA, READ, WRITE
.pdata0xDCF80xDE005.85IDATA, READ
_hvmcode0x553420x554005.07IDATA, EXEC, READ
_hvmuwd0x10000x10000IDATA, READ
PAGE0x2F4C0x30006.28CODE, EXEC, READ
.edata0x00B90x02001.62IDATA, READ
INIT0x16F00x18005.53CODE, EXEC, READ, DISCARD
.rsrc0x09D00x0A003.38IDATA, READ
.reloc0x135C0x14006.13IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score90 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (19)

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.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerKaspersky Lab
Signer organisationKaspersky Lab
IssuerDigiCert High Assurance Code Signing CA-1
SerialF9D91C6ABA86F4E54CBB9EF57E68346
Valid from2017-06-02 00:00 UTC
Valid until2020-07-08 12:00 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about klhk.sys

Is klhk.sys safe?

Based on DriverShield static and dynamic analysis, klhk.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 klhk.sys?

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

What is klhk.sys?

klhk.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Kaspersky Lab.

Related: Other drivers signed by Kaspersky Lab · 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