dxgkrnl.sys - Malicious (88/100) - DriverShield Analysis

Analysis of dxgkrnl.sys: malicious verdict, risk score 88/100. 5 YARA matches, 0/75 multi-engine detections. SHA256 00fd2601b0f574e4. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

dxgkrnl.sys - Analysis Report

DriverShield analyzed the Windows kernel driver dxgkrnl.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches5
Multi-engine detections0 / 75
File size5182920 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-04-02
SHA25600fd2601b0f574e406706472c8fc904893f46ec573c7c3cd724d49641424a78a
SHA1aab8ae16fc72d24eea3fce96821a1ca4a4e52697
MD57653aa510ae9021cad311a9908ac4000

Driver identity

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

File descriptionDirectX Graphics Kernel
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamedxgkrnl.sys
Internal namedxgkrnl.sys
File version!= NULL
Copyright© Microsoft Corporation. All rights reserved.

How the 88/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (54)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
KeAttachProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetSystemInformationhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
KeSetEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 54 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
0x800024B4critical (known exploit)METHOD_BUFFEREDProcess termination (BdApiUtil)
0x00222000medium (known exploit)METHOD_BUFFEREDDriver communication init
0x0080858BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #354
0x00347883highMETHOD_NEITHERFILE_DEVICE_DISK Function #3616
0x0022BBFFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3839
0x00340013highMETHOD_NEITHERFILE_DEVICE_DISK Function #4
0x00808F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #994
0x0080998BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1634
0x0080B9FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3711
0x00347B83highMETHOD_NEITHERFILE_DEVICE_DISK Function #3808
0x00809903highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1600
0x0080878BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #482
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x0080838BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #226
0x00808B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #738
0x0080818BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #98
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x00228307highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #193
0x0022BDB7highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3949
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x008045C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #369
0x00806583highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2400
0x0080860FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #387
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34

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
.text0xA161C0xA20006.19CODE, EXEC, READ
fothk0x10000x10000.07CODE, EXEC, READ
.dxgknpd0x00750x00000READ, WRITE
.rdata0xB8AC80xB90004.44IDATA, READ
.data0x3C200x20001.44IDATA, READ, WRITE
.pdata0x195A80x1A0006.12IDATA, READ
.idata0x5F900x60005.1IDATA, READ
NONPAGE0x00B00x10000.04IDATA, READ, WRITE
PAGE0x2AD7850x2AE0006.36CODE, EXEC, READ
.edata0x34AE0x40005.15IDATA, READ
INIT0x1AE70x20005.52CODE, EXEC, READ, DISCARD
GFIDS0x2A4C0x30004.65IDATA, READ, DISCARD
.rsrc0x964900x970004IDATA, READ
.reloc0x207BC0x210005.92IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (5)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_PhysMemhighPhysical memory mapping
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (19)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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
T1542.001Pre-OS Boot: System FirmwarePersistence
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
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000518418419ADCBAD294F000000000518
Valid from2025-06-19 18:11 UTC
Valid until2026-06-17 18:11 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: 0.

Frequently asked questions about dxgkrnl.sys

Is dxgkrnl.sys safe?

Based on DriverShield static and dynamic analysis, dxgkrnl.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of dxgkrnl.sys?

dxgkrnl.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 00fd2601b0f574e406706472c8fc904893f46ec573c7c3cd724d49641424a78a.

What is dxgkrnl.sys?

dxgkrnl.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact