Vulnerability in Linux
CVE-2025-38614
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.
EPSS: 0.002 (6.0th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Linux — versions 6.6.103, 2.6.33.8, 2.6.38
- Linux Linux_kernel — versions 2.6.38
- Debian Debian_linux — versions 11.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Patch)
- af854a3a-2127-422b-91ae-364da2661108 (Third Party Advisory)
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Frequently asked questions
- What is CVE-2025-38614?
- CVE-2025-38614 is a high-severity vulnerability in Linux, classified under Uncontrolled Recursion. CVSS score: 7.8/10. Published 2025-08-19.
- How severe is CVE-2025-38614?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2025-38614 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.