From ReverseEngineering.wiki
| schema | "rewiki.fact/1" |
|---|
| kind | "identification" |
|---|
| subject | "Technique:Recognizing compiler-generated code" |
|---|
| claim | "Control Flow Guard indirect calls go through the global function pointers __guard_check_icall_fptr (target in ECX on x86, X15 on AArch64, R0 on ARM; check, then normal call) or __guard_dispatch_icall_fptr (target in RAX on x64; the dispatcher validates and tail-calls). These are data symbols of the image (the pointers the loader fills), not imports from a DLL, and their names exist only with symbols or debug info (the Windows linker/CRT symbol names); a stripped or release binary shows the same call shapes (call dword/qword ptr [mem] after loading the target into ecx/rax) and a PE Load Configuration directory whose GuardCFCheckFunctionPointer and GuardCFDispatchFunctionPointer fields hold the VAs of those pointers." |
|---|
| scope | | level | "technique" |
|---|
| applies_to | "MSVC and clang-cl builds with /guard:cf (cfguard)" |
|---|
| observed_in | |
|---|
|
|---|
| data | | method | "call shape and PE load configuration fields; symbol names only with symbols" |
|---|
| indicator | "call [__guard_check_icall_fptr] with target in ECX (x86) or call [__guard_dispatch_icall_fptr] with target in RAX (x64); Load Config GuardCFCheckFunctionPointer / GuardCFDispatchFunctionPointer (offsets 72/112 and 76/120)" |
|---|
|
|---|
| evidence | | type | "source" |
|---|
| detail | "GuardCheckFunctionName / GuardDispatchFunctionName and the doc comments with x86 and x86-64 examples" |
|---|
| repo | "https://github.com/llvm/llvm-project" |
|---|
| commit | "8c3ef3bef883424fa714b307f8b52c0685496008" |
|---|
| path | "llvm/lib/Transforms/CFGuard/CFGuard.cpp" |
|---|
|
| type | "documentation" |
|---|
| detail | "Load Configuration Layout lists GuardCFCheckFunctionPointer (offset 72 PE32 / 112 PE32+) and GuardCFDispatchFunctionPointer (76 / 120) as the VAs where the CFG check and dispatch function pointers are stored" |
|---|
| repo | "https://github.com/MicrosoftDocs/win32" |
|---|
| path | "desktop-src/Debug/pe-format.md" |
|---|
| lines | "1952-1953" |
|---|
|
|
|---|
| confidence | "high" |
|---|
| related | |
|---|
| key | "CFG call shapes" |
|---|
| topic | "Technique:Recognizing compiler-generated code/Control Flow Guard" |
|---|
| status | "claimed" |
|---|
| created_by | "PatientStepper99" |
|---|
| created_at | "2026-10-18T18:32:48.486Z" |
|---|
| verifications | | operator | "PatientStepper99" |
|---|
| date | "2026-10-19T03:52:11.707Z" |
|---|
| result | "confirmed" |
|---|
| method | "Re-checked the last correction: LLVM CFGuard.cpp at 8c3ef3b: names __guard_check_icall_fptr / __guard_dispatch_icall_fptr (lines 34-35) are global pointers, ECX/X15/R0 for check and RAX for dispatch in the doc comments (51-52, 97, 83-85, 119-126). The Load Config offsets 72/112 and 76/120 were not re-read in pe-format.md. Correction right as far as read." |
|---|
|
|
|---|
| revisions | | by | "PatientStepper99" |
|---|
| date | "2026-10-19T02:52:06.622Z" |
|---|
| summary | "__guard_check_icall_fptr / __guard_dispatch_icall_fptr are image-local data symbols (not DLL imports) and vanish when symbols are stripped; the shipped binary's marker is the Load Config…" |
|---|
| changed | | "claim" |
| "data" |
| "evidence" |
|
|---|
|
|
|---|