How derdyast1r/eacbypass-cr3readydrv works
The repository contains two related Windows kernel-driver approaches: a CR3-based request path with a small user-mode client, and a callback-based kernel communication path. The documented goal is driver-to-user-mode communication and process-memory operations, with callback/hooking support; the README explicitly says the setup is incomplete and lists CR3 read/write and other capabilities as work to add. The callback handler excerpts are partial, so unshown dispatch and helper relationships are omitted.
Main entry points: DrvSrc.cpp Hook Control · driver.hpp User Client · main.cpp Driver Entry · utils.hpp CR3 Operations
Components 12
CR3 Request Driver
- User Client
Cr3 Ready Driver/um/driver.hpp - Driver Entry
Cr3 Ready Driver/km/main.cpp - CR3 Operations
Cr3 Ready Driver/km/utils.hpp
Callback Driver
- Hook Control
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/DrvSrc.cpp - Memory Callbacks
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Usermode/CallbackHandler.cpp - Kernel Utilities
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/Utility.cpp - Utility API
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/Utility.h
Protocol Definitions
- Request Types
Cr3 Ready Driver/km/defs.hpp - Callback Protocol
CallbackHandler.h
Other components
- User Application
- Windows win32k
- PEAUTH Driver
Connections 11
- User Application → User Client: uses client
Cr3 Ready Driver/um/driver.hpp - User Client → Driver Entry: sends request
- User Client → Windows win32k: calls resolved function
Cr3 Ready Driver/um/driver.hpp - Driver Entry → CR3 Operations: routes operations
Cr3 Ready Driver/km/main.cpp - Driver Entry → Windows win32k: patches handler
Cr3 Ready Driver/km/main.cpp - CR3 Operations → Request Types: uses definitions
Cr3 Ready Driver/km/utils.hpp - Hook Control → PEAUTH Driver: hooks dispatch
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/DrvSrc.cpp - Hook Control → Memory Callbacks: dispatches callbacks
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/DrvSrc.cpp - Hook Control → Callback Protocol: uses request types
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/DrvSrc.cpp - Memory Callbacks → Kernel Utilities: uses physical helpers
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Usermode/CallbackHandler.cpp - Kernel Utilities → Utility API: implements declarations
cr3 - Ioctl Driver/cr3 - Ioctl Driver/Kernel/Utility.cpp