CVE-2026-46242eventpoll: fix ep_remove struct eventpoll / struct file UAF
- 7.8HighCVSS base score
- 4.6%Exploitation in 30 daysEPSS · top 8.2% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 17 days later
· 17 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 4.6% · top 8.2% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected f2451def095c1743adcfcb0cb5dadc86034e162a – < a10fbbe74e1c743beb1bb312109366667461df8a
- affected a1f93804449d13f97dabd4b996817de4bf1ed67a – < 3e1144d2515d28e4312e663ea05eac203101491d
- affected 58c9b016e12855286370dfb704c08498edbc857a – < 2de4db145b2992da496fea6c51f9839be678ae24
- affected 58c9b016e12855286370dfb704c08498edbc857a – < 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5
- affected 58c9b016e12855286370dfb704c08498edbc857a – < ef4ca02e95363e78977ca04340d44fe3b4b2b81f
- affected 58c9b016e12855286370dfb704c08498edbc857a – < ced39b6a8062bac5c18a1c3df85634107eb8664a
- affected 58c9b016e12855286370dfb704c08498edbc857a – < a6dc643c69311677c574a0f17a3f4d66a5f3744b
- affected 5.15.209 – < 5.15.222
- affected 6.1.175 – < 6.1.178
- affected 6.4
- unaffected < 6.4
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.144 – ≤ 6.6.*
- unaffected 6.12.95 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/a10fbbe74e1c743beb1bb312109366667461df8a (opens in a new tab)
- https://git.kernel.org/stable/c/3e1144d2515d28e4312e663ea05eac203101491d (opens in a new tab)
- https://git.kernel.org/stable/c/2de4db145b2992da496fea6c51f9839be678ae24 (opens in a new tab)
- https://git.kernel.org/stable/c/9324de74a3a59b9fde9b62ee45ebaa71458ba2e5 (opens in a new tab)
- https://git.kernel.org/stable/c/ef4ca02e95363e78977ca04340d44fe3b4b2b81f (opens in a new tab)
- https://git.kernel.org/stable/c/ced39b6a8062bac5c18a1c3df85634107eb8664a (opens in a new tab)
- https://git.kernel.org/stable/c/a6dc643c69311677c574a0f17a3f4d66a5f3744b (opens in a new tab)
- http://www.openwall.com/lists/oss-security/2026/07/08/14 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-33459 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46242)Record last updated .