PoC Monitor
← All CVEs
CVE-2026-46242published 30 May 2026 12:13 UTCData: JSON · API

Linux

eventpoll: fix ep_remove struct eventpoll / struct file UAF

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.

First public PoC 35 daysafter publication · 4 Jul 2026
Public PoCs66 on GitHub
CVSS7.8high · scored by CNA · CWE-416
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= f2451def095c1743adcfcb0cb5dadc86034e162a, < a10fbbe74e1c743beb1bb312109366667461df8a
  • >= a1f93804449d13f97dabd4b996817de4bf1ed67a, < 3e1144d2515d28e4312e663ea05eac203101491d
  • >= 58c9b016e12855286370dfb704c08498edbc857a, < 2de4db145b2992da496fea6c51f9839be678ae24
  • >= 58c9b016e12855286370dfb704c08498edbc857a, < 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5
  • >= 58c9b016e12855286370dfb704c08498edbc857a, < ef4ca02e95363e78977ca04340d44fe3b4b2b81f
  • >= 58c9b016e12855286370dfb704c08498edbc857a, < ced39b6a8062bac5c18a1c3df85634107eb8664a
  • >= 58c9b016e12855286370dfb704c08498edbc857a, < a6dc643c69311677c574a0f17a3f4d66a5f3744b
  • >= 5.15.209, < 5.15.222
  • >= 6.1.175, < 6.1.178

Fixed in a10fbbe74e1c743beb1bb312109366667461df8a, 3e1144d2515d28e4312e663ea05eac203101491d, 2de4db145b2992da496fea6c51f9839be678ae24, 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5, ef4ca02e95363e78977ca04340d44fe3b4b2b81f, ced39b6a8062bac5c18a1c3df85634107eb8664a, a6dc643c69311677c574a0f17a3f4d66a5f3744b, 5.15.222, 6.1.178

Linux Linux
  • 6.4

Fixed in 0, 5.15.222, 6.1.178, 6.6.144, 6.12.95, 6.18.33, 7.0.10, 7.1

Mitigation

Upgrade Linux to a10fbbe74e1c743beb1bb312109366667461df8a or 3e1144d2515d28e4312e663ea05eac203101491d or 2de4db145b2992da496fea6c51f9839be678ae24 or 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5 or ef4ca02e95363e78977ca04340d44fe3b4b2b81f or ced39b6a8062bac5c18a1c3df85634107eb8664a or a6dc643c69311677c574a0f17a3f4d66a5f3744b or 5.15.222 or 6.1.178 or later.

Upgrade Linux to 0 or 5.15.222 or 6.1.178 or 6.6.144 or 6.12.95 or 6.18.33 or 7.0.10 or 7.1 or later.

Timeline

Days relative to CVE publication
t=0+7+14+21+28+35CVE published30 May 2026 · t = 0First public PoC4 Jul 2026 · t+35d

First public PoC 35 days after publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-46242 (created 4 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

6 PoCs · 1 pending · 1 suspicious or fake

PoCs 6
RepositoryCreatedStarsAssessment
0xBlackash/CVE-2026-46242 4 Jul 2026 +35 d 22 PoC
0xredash/CVE-2026-46242 4 Jul 2026 +35 d 22 PoC
ashrafzaryouh/CVE-2026-46242 4 Jul 2026 +35 d 22 PoC
Baba01hacker666/CVE-2026-46242 11 Jul 2026 +42 d 2 PoC
BinaryMasc/CVE-2026-46242 20 Aug 2026 +82 d 0 PoC
villager1314/CVE-2026-46242-Analysis 8 Oct 2026 +131 d 1 PoC
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Pending 1
RepositoryCreatedStarsAssessment
SaithFranklinB/ScannerBadEpoll 8 Jul 2026 +39 d 1 Pending
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Suspicious or fake 1
RepositoryCreatedStarsAssessment
Aayushbankar/bad_epoll_ab_tier2 8 Aug 2026 +70 d 0 Fake

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.