-
CVE-2025-38614
- EPSS 0.06%
- Veröffentlicht 19.08.2025 17:15:40
- Zuletzt bearbeitet 28.08.2025 15:15:55
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- Teams Watchlist Login
- Unerledigt Login
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.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung. Login
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerLinux
≫
Produkt
Linux
Default Statusunaffected
Version <
71379495ab70eaba19224bd71b5b9b399eb85e04
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
1b13b033062824495554e836a1ff5f85ccf6b039
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
2a0c0c974bea9619c6f41794775ae4b97530e0e6
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
7a2125962c42d5336ca0495a9ce4cb38a63e9161
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
ea5f97dbdcb1651581a22bd10afd2f0dd9dc11d6
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
3542c90797bc3ab83ebab54b737d751cf3682036
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version <
f2e467a48287c868818085aa35389a224d226732
Version
22bacca48a1755f79b7e0f192ddb9fbb7fc6e64e
Status
affected
Version
8216e1a0d47cae06a75c42346f19dffe14e42d57
Status
affected
Version
28a92748aa4bc57d35e7b079498b0ac2e7610a37
Status
affected
Version
7eebcd4792c5a341559aed327b6afecbb1c46402
Status
affected
Version
0eccd188cfeaf857a26f2d72941d27d298cf6a54
Status
affected
Version
a72affdbb09f3f24f64ffcbbdf62c2e57c58f379
Status
affected
HerstellerLinux
≫
Produkt
Linux
Default Statusaffected
Version
2.6.38
Status
affected
Version <
2.6.38
Version
0
Status
unaffected
Version <=
5.15.*
Version
5.15.190
Status
unaffected
Version <=
6.1.*
Version
6.1.149
Status
unaffected
Version <=
6.6.*
Version
6.6.103
Status
unaffected
Version <=
6.12.*
Version
6.12.43
Status
unaffected
Version <=
6.15.*
Version
6.15.11
Status
unaffected
Version <=
6.16.*
Version
6.16.1
Status
unaffected
Version <=
*
Version
6.17-rc1
Status
unaffected
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.06% | 0.193 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|