gitwtfhub

wtf is oppo-ghostlock?

pubglite55/oppo-ghostlock — explained in plain English

Analysis updated 2026-05-18

48CAudience · researcherComplexity · 5/5Setup · hard

TL;DR

A security research project attempting to port a Linux kernel exploit called GhostLock to run on an OPPO Find N2 Android phone. The project is blocked by the phone's strict kernel security hardening.

Mindmap

mindmap
  root((repo))
    What it does
      Ports GhostLock to ARM64
      Targets OPPO Find N2
      Security research project
    Tech stack
      C language
      Android NDK
      Makefile build
    Milestones
      Verified Firefox bug
      Leaked kernel addresses
      Triggered GhostLock bug
    Blockers
      CFI bypass failed
      Kernel write blocked
    Status
      In progress
      37 methods tried

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Study how kernel exploits are adapted from x86_64 to ARM64 processors.

REASON 2

Learn about Android kernel security hardening features like CFI and device file restrictions.

REASON 3

Review 37 documented exploitation attempts and understand why each failed.

REASON 4

Use the analysis scripts and test programs to study kernel vulnerability research methods.

What's in the stack?

CAndroid NDKMakefileAndroid Debug Bridge

How it stacks up

pubglite55/oppo-ghostlockdantiicu/wine-nxhuobuilds/quadfs_flight_controller
Stars484848
LanguageCCC
Setup difficultyhardhardhard
Complexity5/55/55/5
Audienceresearcherdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1day+

Requires Android NDK, an OPPO Find N2 phone with ADB access, and deep kernel security knowledge to work with the exploit code.

The explanation does not mention any license for this repository.

Wtf does this do

This repository is a security research project that attempts to adapt a known Linux kernel vulnerability, called GhostLock (CVE-2026-43499), to work on a specific Android phone: the OPPO Find N2. The original exploit was designed for x86_64 computer processors, and the goal here is to translate it to run on ARM64, the processor type used in the phone. The project is written in C and uses Android's Native Development Kit to build the code. The README explains that the project has reached several milestones. The researchers verified a separate Firefox browser vulnerability, leaked certain kernel memory addresses using a technique called KernelSnitch, and successfully triggered the GhostLock bug itself. The code is built by running a Makefile with the NDK toolkit, then pushed to the phone using the Android Debug Bridge tool. The repository organizes its work into folders for the core exploit code, documentation, test programs, and analysis scripts. However, the core goal of the project has not been achieved. The README contains a large log of 37 different methods the researchers tried, and most of them failed. The project is blocked by two main problems. First, they could not bypass a security feature called CFI, which would let them manipulate internal kernel structures. Second, they could not find a way to write data into the kernel's memory, which is required to gain elevated privileges. The root cause is not a flaw in their code, but the phone's strict security configuration. The OPPO kernel blocks all known paths the exploit relies on, such as restricting access to device files and blocking certain system calls. The project is marked as in progress. Several stages passed their tests, but the central blocker around kernel memory access and CFI remains unsolved. The researchers conclude that the OPPO 5.10.236 kernel's security hardening prevents all known GhostLock exploitation paths.

Yoink these prompts

Prompt 1
Help me understand the CFI bypass problem in the oppo-ghostlock project. Why is Control Flow Integrity hard to bypass on the OPPO Find N2 kernel, and what approaches did the researchers try?
Prompt 2
I want to build the oppo-ghostlock exploit code using Android NDK. Walk me through the Makefile setup and how to push the built binary to an Android phone using adb.
Prompt 3
Explain the KernelSnitch technique mentioned in oppo-ghostlock and how it was used to leak kernel memory addresses on the OPPO Find N2.
Prompt 4
Help me analyze why all 37 exploitation methods in the oppo-ghostlock project failed against the OPPO 5.10.236 kernel security hardening. What specific protections blocked each path?

Frequently asked questions

wtf is oppo-ghostlock?

A security research project attempting to port a Linux kernel exploit called GhostLock to run on an OPPO Find N2 Android phone. The project is blocked by the phone's strict kernel security hardening.

What language is oppo-ghostlock written in?

Mainly C. The stack also includes C, Android NDK, Makefile.

What license does oppo-ghostlock use?

The explanation does not mention any license for this repository.

How hard is oppo-ghostlock to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is oppo-ghostlock for?

Mainly researcher.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.