Bad Epoll Linux Kernel Flaw Lets Any User Grab Root, Hits Android

Seoul National University researcher Jaeyoung Chung disclosed CVE-2026-46242, a Linux epoll race condition that lets any local user become root - and even reaches Chrome's renderer sandbox and Pixel 10 handsets.

Key Takeaways

  • Bad Epoll (CVE-2026-46242) is a use-after-free race in the Linux epoll subsystem that lets any local user gain root on kernels 6.4 and newer, including Android devices like the Pixel 10 (kernel 6.6) and Chrome's renderer sandbox.
  • Researcher Jaeyoung Chung of Seoul National University reported the bug via Google's kernelCTF and built an exploit achieving ~99% root success despite a race window only about six machine instructions wide.
  • The flaw survived AI auditing: Anthropic's Mythos model had flagged the same epoll cleanup routine (CVE-2026-43074), but the first patch missed this second race, which took roughly 66 days to fix correctly and evades KASAN detection.
  • There is no workaround since epoll cannot be disabled; the only fix is upstream commit a6dc643c6931, which distributions and cloud operators still need to backport. Kernels on 6.1, including the Pixel 8, are unaffected.
  • No in-the-wild exploitation is known and the bug is not in CISA's KEV catalog, but a public writeup and an in-progress Android rooting chain make rapid patching urgent.

Bad Epoll Linux Kernel Flaw Lets Any User Grab Root, Hits Android

A newly disclosed Linux kernel flaw called Bad Epoll (CVE-2026-46242) lets any local user grab full root access on Linux desktops, servers and Android handsets running kernel 6.4 or newer, and reaches inside Chrome's renderer sandbox on the way. A fix has landed upstream, but distributions still have to ship it before servers are safe.

How A Six-Instruction Window Becomes A Root Shell

Bad Epoll is a use-after-free race in Linux's epoll subsystem, the standard interface that lets a program watch many file descriptors or sockets at once. Two kernel paths try to clean up the same internal object at the same time; one frees the memory while the other is still writing into it. The collision lets an attacker corrupt kernel memory and climb from an unprivileged shell up to root.

The window is narrow, about six machine instructions wide, which makes random attempts almost useless. Seoul National University researcher Jaeyoung Chung, who reported the bug through Google's kernelCTF program, wrote an exploit that widens that window and retries without crashing, reaching root about 99 percent of the time on tested systems and 98 percent on Google's COS-121 target.

Anthropic Project Glasswing AI security research illustration

Why AI Auditing Missed It

The wrinkle is where the bug lives. The same epoll cleanup routine that Anthropic's Mythos AI model flagged earlier this year, netting a fix for CVE-2026-43074, contained a second race. That first patch did not fully address the timing issue, and it took maintainers roughly 66 days to land a correct one. Chung suspects the six-instruction window is simply too tight for the model to see, and once the first bug was patched, the surviving flaw stops tripping KASAN, the kernel's main memory-error detector.

What Sysadmins Should Do Now

Epoll cannot be turned off, and there is no workaround. Kernels built on 6.4 or newer are affected unless they already carry upstream commit a6dc643c6931; older 6.1-based kernels, including some Android handsets like the Pixel 8, are safe because the bug only landed in 6.4. Pixel 10 devices, however, run kernel 6.6 and are in scope. Cloud operators and distribution vendors will need to backport the patch quickly, particularly for hosts that run Chrome renderers or user-facing container workloads. Bad Epoll joins the Bad Binder, Bad IO_uring and Bad Spin family of kernel bugs that have historically become Android rooting tools, dropping alongside Chrome 151's 382 fixes and Adobe's ColdFusion patch storm.

There is no evidence the bug has been exploited in the wild yet. As of publication it is not on CISA's Known Exploited Vulnerabilities catalog, and the only working exploit is the kernelCTF proof of concept. But a public writeup and an in-progress Android chain make that timeline short.

Reporting based on coverage from SecurityWeek, The Hacker News and Tech Times.

Category: AI & Technology

Tags: artificial intelligence

Related Articles

Frequently Asked Questions

What is the Bad Epoll vulnerability (CVE-2026-46242)?

It is a use-after-free race condition in Linux's epoll subsystem where two kernel cleanup paths collide, one freeing memory while the other still writes to it. A local attacker can corrupt kernel memory and escalate from an unprivileged shell to full root.

Which systems are affected by Bad Epoll?

Linux desktops, servers and Android devices running kernel 6.4 or newer without upstream commit a6dc643c6931. Pixel 10 phones (kernel 6.6) are in scope, while 6.1-based kernels such as the Pixel 8 are safe. The bug also reaches inside Chrome's renderer sandbox.

Is Bad Epoll being exploited in the wild?

No evidence of in-the-wild exploitation exists as of publication; it is not in CISA's Known Exploited Vulnerabilities catalog and the only working exploit is the kernelCTF proof of concept. However, a public writeup and an in-progress Android chain shorten that timeline.

How can sysadmins mitigate Bad Epoll?

There is no workaround since epoll cannot be disabled. The only fix is applying the upstream kernel patch (commit a6dc643c6931), so admins should update kernels as soon as distributions ship backports, prioritizing hosts running Chrome renderers or user-facing container workloads.