LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48620: uev (aka libuev) before 2.4.1 has a buffer overflow in epoll_wait if maxevents is a large number.

uev (aka libuev) before 2.4.1 has a buffer overflow in epoll_wait if maxevents is a large number.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-48620 is a critical memory-safety flaw in uev/libuev before 2.4.1. A very large event count can trigger a buffer overflow in epoll_wait handling. The highest urgency is for systems where libuev is used by network-facing or privileged services.

Executive priority

Treat as high-priority patching where libuev is present in exposed or privileged services. Do not assume broad enterprise exposure from the CVE alone; first confirm whether the library is deployed directly or bundled by vendors.

Technical view

The CVE describes a CWE-120 buffer overflow in uev/libuev before 2.4.1 when epoll_wait receives a large maxevents value. The record assigns CVSS 3.1 score 9.8 with network, no-auth, no-user-interaction characteristics. Upstream references show a v2.4.1 fix and Fedora/Debian advisories.

Likely exposure

Exposure is likely limited to applications, appliances, or Linux packages that embed or dynamically link uev/libuev before 2.4.1. The supplied CVE data does not name specific affected products or CPEs, so dependency inventory is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical risk depends on whether an application can reach the vulnerable epoll_wait path with an untrusted or oversized maxevents value.

Researcher notes

The public record is sparse: no CPEs, no affected application list, and no KEV signal. Analysis should focus on upstream diff/commit review, distro backport mapping, and reachable call paths in applications using libuev.

Mitigation direction

  • Upgrade uev/libuev to 2.4.1 or a distribution backport containing the fix.
  • Apply relevant Fedora or Debian security updates where those packages are in use.
  • Check vendor guidance for products that bundle libuev internally.
  • Prioritize remediation for internet-facing, privileged, or high-availability services using libuev.
  • Restart affected services after patching dynamically linked libraries.

Validation and detection

  • Inventory installed libuev or uev packages and embedded copies.
  • Check SBOMs and build manifests for libuev versions before 2.4.1.
  • Confirm patched packages using distribution advisory version information.
  • Identify services linked against libuev and their exposure level.
  • Review vendor appliance advisories for bundled libuev status.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-48620 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-48620Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-120

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs