CVE-2026-46242: Linux vulnerability
Vendor fix available · Affected: Linux · Exploitation: public proof of concept (unverified)
ExploitationProof of concept public
Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)
- In CISA KEV: not seen
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public5 public GitHub repositories (unverified), listed by PoC-in-GitHub4 Jul
- Not established: not seen
Higher than 91% of scored CVEs
DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
What changed
- PoC-in-GitHub lists 5 public GitHub repositories (unverified) PoC-in-GitHub
Coverage4 articles · 3 outlets
One row per outlet, in order of first report. First in our coverage: Security Affairs, 6 Jul.
- Mon 6 Jul, 09:31 UTC. Security Affairs, first report. CVE-2026-46242: Linux Epoll Flaw Grants Local Root Access.
- Mon 6 Jul, 13:31 UTC. SecurityWeek, its first report on the story. CVE-2026-46242: Linux 'Bad Epoll' flaw lets attackers gain root.
- Tue 14 Jul, 17:16 UTC. SecurityOnline, its first report on the story. Linux Kernel Bug Lets Users Gain Root Access via Bad Epoll.
- Tue 14 Jul, 17:20 UTC. SecurityOnline. Public Exploit and Details Released for Bad Epoll Root Flaw (CVE-2026-46242).
- First report
- Article
- Running total
Show as tableHide table
| Published (UTC) | Outlet | Headline |
|---|---|---|
| 6 Jul 09:31 | Security Affairs | CVE-2026-46242: Linux Epoll Flaw Grants Local Root Access |
| 6 Jul 13:31 | SecurityWeek | CVE-2026-46242: Linux 'Bad Epoll' flaw lets attackers gain root |
| 14 Jul 17:16 | SecurityOnline | Linux Kernel Bug Lets Users Gain Root Access via Bad Epoll |
| 14 Jul 17:20 | SecurityOnline | Public Exploit and Details Released for Bad Epoll Root Flaw (CVE-2026-46242) |
- CVE-2026-46242: Linux Epoll Flaw Grants Local Root AccessSecurity Affairs · first in our coverage
New articles also arrive in the RSS feed.