Operating-system internals · Kernel & syscall fuzzing · Reverse engineering · Binary exploitation
I go all the way to the metal — from raw sockets and memory forensics to writing a complete
x86-64 operating system and the coverage-guided fuzzer that hardens it.
Projects · LinkedIn · X / Twitter
MAKH is a higher-half x86-64 kernel and userspace built entirely from scratch in C and assembly — no Linux, no existing kernel underneath. It is both a real OS and a research platform for kernel security and coverage-guided fuzzing.
- Kernel: higher-half x86-64, Multiboot2/GRUB boot, preemptive scheduler, ELF loader, POSIX-style signals, threads & futexes, virtual memory (mmap/mprotect/munmap, fork).
- Userspace (ring 3): 80 syscalls, an interactive shell, pipes, job control, TLS.
- Storage & net: a VFS with ext2 (read/write, indirect blocks, directory ops), tmpfs, devfs, and a TCP/IP stack (e1000 driver, sockets, DNS, ICMP).
- Self-hosting: compiles real programs on itself — tcc, make, and musl-linked tools.
- Security research core: KFUZZ (ring-0 coverage-guided kernel fuzzer) and UFUZZ (ring-3 syscall fuzzer with a typed-program IR, layered oracles, and resource-leak detection), in the spirit of syzkaller / KCOV / KASAN — but co-designed with the kernel it tests.
- Evidence-driven: every hardening fix ships with a fail-first regression test and a CI gate.
Honest by rule —
PASS_QEMUis never claimed asPASS_HARDWARE.
If you care about OSDev, bare-metal x86-64, kernel exploitation surfaces, or how a coverage-guided syscall fuzzer actually works end-to-end, MAKH is built to be read.
- Operating-system internals, kernel attack surfaces, and syscall-ABI hardening
- Coverage-guided fuzzing (kernel & userspace), sanitizers, and fault oracles
- Binary analysis, patching, and exploit development (ROP, shellcode)
- Network packet crafting and behavioral OS fingerprinting
- Memory & file forensics, side-channel research
- Next deep dives: hypervisor security · SMP race fuzzing · firmware/IoT low-level · secure boot
| Project | Description | Tech |
|---|---|---|
| MAKH | From-scratch x86-64 OS: higher-half kernel, ext2, TCP/IP, self-hosting (tcc/make), and the KFUZZ/UFUZZ coverage-guided fuzzers | C · x86-64 asm |
| Raw_Overflow_Forge | All-in-one ROP exploitation engine: automated binary analysis, gadget chaining, payload generation | Python |
| shellcode_Weaver | Shellcode generator, mutator, and analyzer for research & education | Python |
| Privilege-Escalator | Linux privilege-escalation scanner with parallel vector probing and intelligent chaining | Bash |
| Packet Phantom | Network recon: advanced port scanning, 9-dimensional behavioral OS fingerprinting, evasion suite | Python (Scapy) |
All tooling is built for authorized testing, education, and red/blue-team practice.
- MAKH: UFUZZ bricks U5→U10 — oracle framework, crash triage & minimization, corpus/mutation, single-CPU race mode, then target harnesses; SMP fuzzing after the SMP kernel lands.
- Offensive toolkit: ARP Reaper · WiFi Ghost Buster · MITM Labyrinth · Memory Ghost Carver · Key Bleeder · File Resurrectionist · Cloud Shadow Enum · Risk Labyrinth Mapper.
Languages: C · x86-64 Assembly · Python · Bash
Domains: OS development · Kernel security · Fuzzing · Reverse engineering · Exploit development · Network security · Digital forensics
Style: from-scratch, minimal-dependency, evidence-first — reproducible or it didn't happen.
- LinkedIn: @lakhemissi · X: @X4m1n3 · GitHub: @medaminkh-dev
- Open to collaboration on OS development, kernel fuzzing, CTF tooling, and low-level security research.
“The closer you get to the metal, the more you understand the system — and the more dangerous you become.”
— Building in public, one commit at a time.
Keywords: operating system from scratch · x86-64 kernel development · osdev · bare metal · coverage-guided fuzzing · kernel fuzzer · syscall fuzzing · syzkaller-style · ext2 · self-hosting OS · binary exploitation · reverse engineering · security research