Home
» Security vulnerabilities
» CVE-2022-48620
uev (aka libuev) before 2.4.1 has a buffer overflow in epoll_wait if maxevents is a large number.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-48620
Conclusion & alert: CVE-2022-48620 is rated Moderate Risk (63.3/100) : CVSS Critical severity, with medium exploitation likelihood (EPSS 1.33%).Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2022-48620
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.82%
1.33%
+0.51%
2
2026-06-01
1.09%
0.82%
-0.28%
3
2026-02-03
—
1.09%
—
Full EPSS history
(16 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-48620
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
9.8
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
5.9
[email protected]
9.8
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
5.9
134c704f-9b21-4f2e-91b3-4a467353bcc0
Weakness enumeration for CVE-2022-48620
OS Trackers for CVE-2022-48620
vendor
priority
summary
link
debian
not yet assigned
CVE-2022-48620 not yet assigned priority: Debian including 1 source packages (libuev), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.
https://security-tracker.debian.org/tracker/CVE-2022-48620
ubuntu
medium
CVE-2022-48620 medium priority: Ubuntu including 1 source packages (libuev), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needs-triage 4, DNE 1.
https://ubuntu.com/security/CVE-2022-48620
Affected software / configurations for CVE-2022-48620
Vendor
Product
Version
Raw CPE
troglobit
libeuv
< 2.4.1
cpe:2.3:a:troglobit:libeuv:*:*:*:*:*:*:*:*
References for CVE-2022-48620
cvelogic
Threat Intelligence