In the Linux kernel, the following vulnerability has been resolved:
eventpoll: Fix semi-unbounded recursion
Ensure that epoll instances can never form a graph deeper than
EP_MAX_NESTS+1 links.
Currently, ep_loop_check_proc() ensures that the graph is loop-free and
does some recursion depth checks, but those recursion depth checks don't
limit the depth of the resulting tree for two reasons:
- They don't look upwards in the tree.
- If there are multiple downwards paths of different lengths, only one of
the paths is actually considered for the depth check since commit
28d82dc1c4ed ("epoll: limit paths").
Essentially, the current recursion depth check in ep_loop_check_proc() just
serves to prevent it from recursing too deeply while checking for loops.
A more thorough check is done in reverse_path_check() after the new graph
edge has already been created; this checks, among other things, that no
paths going upwards from any non-epoll file with a length of more than 5
edges exist. However, this check does not apply to non-epoll files.
As a result, it is possible to recurse to a depth of at least roughly 500,
tested on v6.15. (I am unsure if deeper recursion is possible; and this may
have changed with commit 8c44dac8add7 ("eventpoll: Fix priority inversion
problem").)
To fix it:
1. In ep_loop_check_proc(), note the subtree depth of each visited node,
and use subtree depths for the total depth calculation even when a subtree
has already been visited.
2. Add ep_get_upwards_depth_proc() for similarly determining the maximum
depth of an upwards walk.
3. In ep_loop_check(), use these values to limit the total path length
between epoll nodes to EP_MAX_NESTS edges.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel epoll flaw where nested event polling structures could become much deeper than intended. That may allow excessive kernel recursion and reliability impact. The sources do not provide CVSS, CWE, privilege requirements, or confirmed impact details, so urgency should be driven by kernel exposure and vendor advisories.
Executive priority
Address in the normal kernel patch cycle, escalating for shared hosting, appliance fleets, or systems accepting untrusted local workloads. No source confirms active exploitation, but kernel flaws can carry broad operational risk.
Technical view
The kernel fix constrains epoll graph depth to EP_MAX_NESTS by tracking subtree and upward depths during ep_loop_check(). The issue existed because prior checks avoided loops but did not fully bound resulting path depth, with testing showing recursion around 500 levels on v6.15.
Likely exposure
Systems running affected Linux kernel versions from 2.6.38 through the listed fixed stable releases may be exposed. Exposure also applies to products that embed affected Linux kernels, as indicated by Debian LTS and Siemens advisories.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or weaponized abuse. Treat this as a kernel reliability and hardening issue until vendor advisories provide more impact detail.
Researcher notes
The key weakness is incomplete epoll graph-depth enforcement, not loop detection alone. The provided description says reverse_path_check() did not cover all relevant paths, permitting much deeper recursion than EP_MAX_NESTS intended.
Mitigation direction
Apply fixed Linux kernel updates from your distribution or product vendor.
Prioritize internet-facing, multi-tenant, and untrusted-user Linux systems.
For appliances, follow Siemens or other OEM advisories before changing kernels.
Track Debian LTS updates where Debian kernels are in use.
Validation and detection
Inventory running kernel versions across servers, containers hosts, and appliances.
Compare versions against affected and fixed ranges in the CVE record.
Confirm vendor advisories for embedded or managed Linux products.
Verify patched systems boot into the updated kernel.
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.
cve · low confidence lookup
CVE-2025-38614 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
2ADP providers
12Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 19, 2025, 17:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.