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

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

phymemx64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver phymemx64.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).

Verdict	Vulnerable (72/100)
YARA matches	0
Multi-engine detections	0 / 75
File size	26104 bytes
Code-signing signer	Symantec Time Stamping Services CA - G2
Analyzed	2026-09-06
SHA256	19a212e6fc324f4cb9ee5eba60f5c1fc0191799a4432265cbeaa3307c76a7fc0
SHA1	f42f28d164205d9f6dab9317c9fecad54c38d5d2
MD5	715572dfe6fb10b16f980bfa242f3fa5

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	0 / 100
Dangerous kernel imports	78 / 100
IOCTL dispatch surface	51 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (10)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
KeBugCheckEx	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
IofCompleteRequest	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard 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.

Code	Severity	Transfer	Description
0x00222000	medium (known exploit)	METHOD_BUFFERED	Driver communication init
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x0D3E	0x0E00	5.92	CODE, EXEC, READ
.rdata	0x04E4	0x0600	3.45	IDATA, READ
.data	0x0F28	0x0200	0.61	IDATA, READ, WRITE
.pdata	0x00D8	0x0200	1.81	IDATA, READ
.gfids	0x0004	0x0200	0.04	IDATA, READ
INIT	0x031E	0x0400	4.15	CODE, EXEC, READ, DISCARD
.reloc	0x0024	0x0200	0.37	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	55 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Time Stamping Services CA - G2
Signer organisation	Symantec Corporation
Issuer	Thawte Timestamping CA
Serial	7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from	2012-12-21 00:00 UTC
Valid until	2020-12-30 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Symantec Time Stamping Services Signer - G4
Chain: Huawei Technologies Co.,Ltd.
Chain: VeriSign Class 3 Public Primary Certification Authority - G5
Chain: VeriSign Class 3 Code Signing 2010 CA

Symbolic execution

Engine angr, status completed, 43 paths explored at a maximum depth of 43. Vulnerability classes reached: 1. 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 phymemx64.sys

Is phymemx64.sys safe?

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

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

What is phymemx64.sys?

phymemx64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.