CVE-2025-38614

MediumCVSS 5.5/10Last modified Nov 10, 2026

Description

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.

Metrics

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

Weakness enumeration

Affected software

VendorProductVersions
LinuxLinux>= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < 71379495ab70eaba19224bd71b5b9b399eb85e04; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < 1b13b033062824495554e836a1ff5f85ccf6b039; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < 2a0c0c974bea9619c6f41794775ae4b97530e0e6; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < 7a2125962c42d5336ca0495a9ce4cb38a63e9161; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < ea5f97dbdcb1651581a22bd10afd2f0dd9dc11d6; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < 3542c90797bc3ab83ebab54b737d751cf3682036; >= 22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e, < f2e467a48287c868818085aa35389a224d226732; 8216e1a0d47cae06a75c42346f19dffe14e42d57; 28a92748aa4bc57d35e7b079498b0ac2e7610a37; 7eebcd4792c5a341559aed327b6afecbb1c46402; 0eccd188cfeaf857a26f2d72941d27d298cf6a54; a72affdbb09f3f24f64ffcbbdf62c2e57c58f379; >= 2.6.32.30, < 2.6.33; >= 2.6.33.8, < 2.6.34; >= 2.6.34.10, < 2.6.35; >= 2.6.35.12, < 2.6.36; >= 2.6.37.3, < 2.6.38
LinuxLinux2.6.38
SiemensSIMATIC CN 4100< V5.0
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.6, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.7, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.6, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.7, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.6, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.7, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.6, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.7, < *
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.6, < *
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.7, < *

References

Timeline

Published
Aug 19, 2025
Last modified
Nov 10, 2026
NVD status
Modified

Related CVEs from 2025

CVE-2025-386155.5In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: cancle set bad inode after removing name fails The reproduceCVE-2025-386167.1In the Linux kernel, the following vulnerability has been resolved: tls: handle data disappearing from under the TLS ULP TLS expects that CVE-2025-386174.7In the Linux kernel, the following vulnerability has been resolved: net/packet: fix a race in packet_set_ring() and packet_notifier() WhenCVE-2025-386187.8In the Linux kernel, the following vulnerability has been resolved: vsock: Do not allow binding to VMADDR_PORT_ANY It is possible for a vsCVE-2025-386195.5In the Linux kernel, the following vulnerability has been resolved: media: ti: j721e-csi2rx: fix list_del corruption If ti_csi2rx_start_dmCVE-2025-38625.4Contest Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ parameter in all versions up to, and includinCVE-2025-386207.8In the Linux kernel, the following vulnerability has been resolved: zloop: fix KASAN use-after-free of tag set When a zoned loop device, oCVE-2025-386215.5In the Linux kernel, the following vulnerability has been resolved: md: make rdev_addable usable for rcu mode Our testcase trigger panic: CVE-2025-386225.5In the Linux kernel, the following vulnerability has been resolved: net: drop UFO packets in udp_rcv_segment() When sending a packet with CVE-2025-386235.5In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Fix surprise plug detection and recovery The existing PoCVE-2025-386245.5In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Clean up allocated IRQs on unplug When the root of a nesCVE-2025-386255.5In the Linux kernel, the following vulnerability has been resolved: vfio/pds: Fix missing detach_ioas op When CONFIG_IOMMUFD is enabled an