How joelfm4/kernel-driver works
This repository pairs a Windows user-mode application with a kernel driver for inspecting and reading or writing a selected process. The documented workflow is to load the driver, start a target application, then run the client: its MemoryManager opens the driver, finds and attaches to the target, and looks up a module base. The driver dispatches buffered I/O requests and uses MmCopyVirtualMemory for transfers. The graph reflects the excerpts and README; it does not assume behavior beyond the sampled code, and the documented main loop has no shown implementation.
Main entry points: Memory.h MemoryManager · Driver.cpp Control dispatch · Main.cpp Application entry · Driver.h IOCTL request protocol
Components 16
User-mode client
- Application entry
Application/Source/Main.cpp - MemoryManager
Application/Source/Memory/Memory.h - Process discovery
Application/Source/Memory/Memory.h - Module lookup
Application/Source/Memory/Memory.h - Memory transfer API
Application/Source/Memory/Memory.h - Console logging
Application/Source/Logger/Logger.h
Kernel driver
- Driver device
Driver/Source/Driver.cpp - Driver entry
Driver/Source/Driver.cpp - Device setup
Driver/Source/Driver.cpp - IRP handlers
Driver/Source/Driver.cpp - Control dispatch
Driver/Source/Driver.cpp - Process attachment
Driver/Source/Driver.cpp - Virtual memory copy
Driver/Source/Driver.cpp
Driver protocol
- IOCTL request protocol
Driver/Source/Driver.h
Other components
- Operator
- Target process
Connections 22
- Operator → Application entry: starts
README.md - Operator → Target process: starts
README.md - Application entry → MemoryManager: constructs
Application/Source/Main.cpp - Application entry → Module lookup: queries base
Application/Source/Main.cpp - Application entry → Console logging: logs status
Application/Source/Main.cpp - MemoryManager → Process discovery: finds process
Application/Source/Memory/Memory.h - MemoryManager → Driver device: opens device
Application/Source/Memory/Memory.h - MemoryManager → Process attachment: requests attach
Application/Source/Memory/Memory.h - MemoryManager → IOCTL request protocol: uses requests
Application/Source/Memory/Memory.h - Process discovery → Target process: matches name
Application/Source/Memory/Memory.h - Module lookup → Target process: enumerates modules
Application/Source/Memory/Memory.h - Memory transfer API → Control dispatch: sends IOCTL
README.md - MemoryManager → Memory transfer API: provides
Application/Source/Memory/Memory.h - Driver entry → Device setup: calls
Driver/Source/Driver.cpp - Device setup → Driver device: creates and links
Driver/Source/Driver.cpp - Device setup → IRP handlers: registers
Driver/Source/Driver.cpp - IRP handlers → Control dispatch: dispatches control
Driver/Source/Driver.cpp - Control dispatch → IOCTL request protocol: decodes requests
Driver/Source/Driver.cpp - Control dispatch → Process attachment: handles attach
Driver/Source/Driver.cpp - Control dispatch → Virtual memory copy: copies memory
Driver/Source/Driver.cpp - Process attachment → Target process: looks up PID
Driver/Source/Driver.cpp - Virtual memory copy → Target process: reads or writes
Driver/Source/Driver.cpp