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

Analysis of rtkio.sys: vulnerable verdict, risk score 72/100. 5 YARA matches, 1/76 multi-engine detections. SHA256 478917514be37b32. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

rtkio.sys - Analysis Report

DriverShield analyzed the Windows kernel driver rtkio.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 matches5
Multi-engine detections1 / 76
File size17216 bytes
Code-signing signerDigiCert High Assurance EV Root CA
Analyzed2026-09-08
SHA256478917514be37b32d5ccf76e4009f6f952f39f5553953544f1b0688befd95e82
SHA1166759fd511613414d3213942fe2575b926a6226
MD5daf800da15b33bf1a84ee7afc59f0656

Driver identity

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

File descriptionRealtek IODriver
ProductWindows (R) Codename Longhorn DDK driver
CompanyWindows (R) Codename Longhorn DDK provider
Original filenamertkio.sys
Internal namertkio.sys
File version6.0.6000.16386 built by: WinDDK
Copyright© Microsoft Corporation. All rights reserved.

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 matches95 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface6 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
WRITE_PORT_ULONGhighPotentially dangerous - could be used for privilege escalation or security bypass
READ_PORT_ULONGhighPotentially dangerous - could be used for privilege escalation or security bypass
WRITE_PORT_UCHARhighPotentially dangerous - could be used for privilege escalation or security bypass
READ_PORT_UCHARhighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ExAllocatePoollowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteDevicelowStandard 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.

CodeSeverityTransferDescription
0x0080BF57highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #4053
0x003403A8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #234

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x076E0x07805.95CODE, EXEC, READ
.rdata0x01640x01803.56IDATA, READ
.data0x000C0x00800.52IDATA, READ, WRITE
PAGE0x06630x06806.19CODE, EXEC, READ
INIT0x049E0x05005.5CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x04080x04803.14IDATA, READ, DISCARD
.reloc0x01340x01804.34IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (5)

RuleSeverityDetects
PUA_VULN_Driver_Windowsrcodenamelonghornddkprovider_Rtkiosys_Windowsrcodenamelonghornddkdr...mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - rtkio.sys, rtkio64.sys, rtkiow8x64.sys, rtkiow10x64.sys. Investigate matches...
PUA_VULN_Driver_Windowsrcodenamelonghornddkprovider_Rtkiosys_Windowsrcodenamelonghornddkdr...mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - rtkio.sys, rtkio64.sys, rtkiow8x64.sys, rtkiow10x64.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping
SUSP_PortIOmediumDirect port I/O

MITRE ATT&CK techniques (15)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
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 High Assurance EV Root CA
Signer organisationDigiCert Inc
IssuerMicrosoft Code Verification Root
Serial61204DB4000000000027
Valid from2011-04-15 19:45 UTC
Valid until2021-04-15 19:55 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 3 paths explored at a maximum depth of 3. 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 rtkio.sys

Is rtkio.sys safe?

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

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

What is rtkio.sys?

rtkio.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 High Assurance EV Root CA.

Related: Other drivers signed by DigiCert High Assurance EV Root CA · 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