Loading vulnerability…
CVE-2026-46242 is a use-after-free vulnerability in the Linux kernel eventpoll subsystem. The flaw is in ep_remove() via ep_remove_file(), where file->f_ep is cleared under file->f_lock and the code continues to use the associated struct file within the same critical section. A concurrent __fput() can observe the transient NULL in file->f_ep, take the eventpoll_release() fast path, skip eventpoll_release_file(), and proceed to f_op->release and file_free() while ep_remove() is still operating on the object. In the epoll-watches-epoll case, this can lead to ep_eventpoll_release() -> ep_clear_and_put() -> ep_free() freeing the watched struct eventpoll while ep_remove() still uses pointers into its embedded refs hlist_head, causing hlist_del_rcu() to write into freed kmalloc-192 memory. Because struct file is SLAB_TYPESAFE_BY_RCU, the backing slot for the file object may also be recycled by alloc_empty_file() while ep_remove() is still nominally inside file->f_lock, reinitializing f_lock and f_ep and creating a second unsafe condition. The upstream fix pins the file with epi_fget() at the start of ep_remove() and only enters the critical section if the pin succeeds, preventing __fput() from reaching refcount zero and keeping both the struct file and watched struct eventpoll alive for the duration of the operation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.