Cyber Security News[verified]@The_Cyber_NewsDisclosure
Newly disclosed CVE‑2026‑46242, dubbed "Bad Epoll", is a race‑condition and use‑after‑free flaw in the Linux kernel’s epoll subsystem that allows local users to gain root on Linux servers, desktops and Android devices. No PoC, patch, or active exploitation information is provided, only technical details of the vulnerability.
J-jaeyoung[verified]@J_jaey0ungPoC
The author announces discovering a race condition in Linux epoll (CVE-2026-46242), provides a proof‑of‑concept exploit that achieves root on the Google kernelCTF platform, and suggests possible Android impact.
0xor0ne[verified]@0xor0nePoC
The tweet announces a race‑condition use‑after‑free vulnerability in Linux’s epoll (CVE‑2026‑46242) and links to a GitHub repo containing a POC. It does not mention patches, active exploitation, or false‑positive claims.
dbugs[verified]@ptdbugsPoC
A proof‑of‑concept exploit for CVE‑2026‑46242 has been published, detailing a race condition in the Linux kernel’s epoll subsystem that results in a use‑after‑free and privilege escalation; however, no real‑world exploitation or patch information is mentioned.
إبراهيم بوحيمد | Ibrahim Buhaimed[verified]@buhaimediDisclosure
The text announces the discovery of a race-condition vulnerability in the Linux kernel's Bad Epoll component (CVE-2026-46242) by researcher Jaeyoung Chung.
辻 伸弘 (nobuhiro tsuji)[verified]@ntsujiDisclosure
A newly disclosed Linux kernel use‑after‑free flaw (CVE‑2026‑46242, "Bad Epoll") can grant local users root privileges; no active exploitation or patch information has been noted.
Rıdvan Yağlı[verified]@ridvanyagliPoC
Bad Epoll (CVE‑2026‑46242) is a use‑after‑free race condition that can lead to root escalation, and a functional PoC with ~99% success has been published on GitHub, though no active exploitation or patch is reported.
kokumօtօ[verified]@__kokumotoDisclosure
The post discloses a new Linux kernel privilege‑escalation flaw (CVE‑2026‑46242) affecting Android, capable of being triggered after memory release and usable from Chrome’s renderer sandbox, with no mitigation currently available beyond awaiting an upstream patch.