Android’s core is well hardened, but every phone maker adds its own drivers and services on top. In OEMpocalypse Now, the first of a four-part series, Calif’s Lukas Maar shows a single strategy that takes an ordinary app with no permissions to full root on current flagships from several brands.

Phones tested

  • Samsung: Galaxy S26 Ultra, Galaxy S26 (Exynos) and Galaxy S23. The research says S23 to S26 and recent Z models are in scope.
  • Xiaomi: Xiaomi 17, with most mid-range to flagship models in scope.
  • Oppo, OnePlus and Realme: Oppo Find X9 Ultra, OnePlus Ace 6 Ultra and other recent flagships.

All ran the latest firmware as of early August 2026, with a locked bootloader and verified boot showing green.

How it works, in plain terms

Each chain uses at least two bugs. First, a logic flaw in a phone maker’s own system service, such as a missing check on who is calling, lets the app reach a protected driver. Second, a memory-page use-after-free in that driver: it hands a page of memory back to the system while still able to read and write it. With that, the app can rewrite kernel memory and become root.

The author says none of these bugs are subtle, and that page-level bugs like this get around many of the kernel’s usual defences. The same memory-reuse behaviour was unchanged from kernel 5.15 through 6.12, which is why one strategy works across brands.

What is not stated yet

The first part does not list CVE numbers or patch status for each bug. The brand-specific parts (Samsung, Xiaomi, Oppo/OnePlus/Realme) are still to come.

What to do now

  • Install every monthly security update from your phone maker as soon as it arrives. Prefer models with a long, regular update promise.
  • Only install apps from trusted stores, and be wary of sideloaded APKs: this attack starts with you running an app.
  • Companies: use Android Enterprise / MDM to enforce a minimum security patch level and block unknown sources on work phones.
  • Phone makers and driver teams: audit drivers that map memory into apps or devices, make sure every mapping is removed before a page is freed, and lock driver access behind strict SELinux rules.

Not sure if this affects you? Talk to us and we will check your Android device policy and plan the update with you.

Source

This article summarises OEMpocalypse Now: A Generic Exploitation Strategy from Android untrusted app to root, published by Calif on 31 August 2026 (research by Lukas Maar). Read the original for the full technical details.