Memory corruption via oversized epoll event count
Published Jan 12, 2024 · Updated Jan 25, 2026
Buffer overflow in troglobit libuev before 2.4.1 allows attackers to corrupt memory via an excessive event-cache size. In uev_run(), a fixed 10-entry struct epoll_event stack array is passed to epoll_wait() with ctx->maxevents, which uev_init1() does not cap. The condition requires a calling application to supply a value above 10 and enough simultaneous events for the kernel to write past the array, producing memory corruption or a crash.
Summary
What happened
Buffer overflow in troglobit libuev before 2.4.1 allows attackers to corrupt memory via an excessive event-cache size. In uev_run(), a fixed 10-entry struct epoll_event stack array is passed to epoll_wait() with ctx->maxevents, which uev_init1() does not cap. The condition requires a calling application to supply a value above 10 and enough simultaneous events for the kernel to write past the array, producing memory corruption or a crash.
The record
- CVE
- CVE-2022-48620
- Published
- Jan 12, 2024
- Updated
- Jan 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2024CVE publishedPublication date reported by the CVE source.
- Jan 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo