CVE-2022-48620
Troglobit Libeuv buffer overflow
- Published12 Jan 2024
Description
uev (aka libuev) before 2.4.1 has a buffer overflow in epoll_wait if maxevents is a large number.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/troglobit/libuev/commit/2d9f1c9ce655cc38511aeeb6e95ac30914f7aec9
- https://github.com/troglobit/libuev/compare/v2.4.0...v2.4.1
- https://github.com/troglobit/libuev/issues/27
- https://lists.debian.org/debian-lts-announce/2026/01/msg00026.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2J4UB4KXWCCTZCE53B6SFIREZ57INK7T/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E6RLVLJGDKTEVJP446TFDANHB4LHRAOP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/P2XZESYGE6XDWAPFUOX26ZWJV2JWMMM5/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/2J4UB4KXWCCTZCE53B6SFIREZ57INK7T/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/E6RLVLJGDKTEVJP446TFDANHB4LHRAOP/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/P2XZESYGE6XDWAPFUOX26ZWJV2JWMMM5/
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-48620 being actively exploited?
CVE-2022-48620 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.32%.
How severe is CVE-2022-48620?
CVE-2022-48620 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.32% probability of exploitation.
Which products are affected by CVE-2022-48620?
Affected products include Troglobit Libeuv.
How do I fix CVE-2022-48620?
Upgrade affected software to a fixed version, for example Troglobit Libeuv 2.4.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-48620 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.