Kestrel
대시보드로 돌아가기
CVE-2025-38614MEDIUM· 5.5MITRENVD대응게시일: 2025. 08. 19.수정일: 2026. 07. 14.CNA: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Modified

In the Linux kernel, the following vulnerability has been resolved: eventpoll: Fix semi-unbounded recursion Ensure that epoll instances ca

위협 신호 · CVSS · EPSS · KEV

정기 패치· 높은 악용 신호 없음
CVSS
5.5medium

이론적 심각도 점수

EPSS
0.2%상위 94.0%

30일 내 악용 확률 예측

KEV
미등재

실측 악용 기록 없음

권장 대응 기한차기 업그레이드 시CISA SSVC 기준

별도 긴급 패치 불필요 — 정기 시스템 업그레이드 주기에 맞춰 조치

· KEV 미등재 · 자동화 어려움 · 부분 영향 · 내부 한정

CVSS 벡터 · 메트릭

악용 경로
공격 벡터로컬
공격 복잡도낮음
필요 권한낮음
사용자 상호작용불필요
범위불변
영향
기밀성 영향없음
무결성 영향없음
가용성 영향높음
버전별 점수
CVSS 3.15.5MEDIUM· 악용성 1.8· 영향도 3.6
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

약점 (CWE)

  • CWE-674

    제어되지 않는 재귀 — 무한/과도 재귀로 자원 고갈(DoS).

상세 설명

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.

AI 심층 분석

공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.

영향받는 제품·버전

  • linux linux_kernel2.6.32.30 - 2.6.33
    linux
  • linux linux_kernel2.6.33.8 - 2.6.34
    linux
  • linux linux_kernel2.6.34.10 - 2.6.35
    linux
  • linux linux_kernel2.6.35.12 - 2.6.36
    linux
  • linux linux_kernel2.6.37.3 - 2.6.38
    linux
  • linux linux_kernel2.6.38.1 - 5.15.190
    linux
  • linux linux_kernel5.16 - 6.1.149
    linux
  • linux linux_kernel6.2 - 6.6.103
    linux
  • linux linux_kernel6.7 - 6.12.43
    linux
  • linux linux_kernel6.13 - 6.15.11
    linux
  • linux linux_kernel6.16 - 6.16.1
    linux
  • linux linux_kernel
    linux
  • linux linux_kernel
    linux
  • linux linux_kernel
    linux
  • debian debian_linux
    linux

영향받는 구성 (CPE) 5

  • linux linux_kernel≥ 2.6.32.30 < 2.6.33cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
  • linux linux_kernel 2.6.38cpe:2.3:o:linux:linux_kernel:2.6.38:-:*:*:*:*:*:*
  • linux linux_kernel 2.6.38cpe:2.3:o:linux:linux_kernel:2.6.38:rc7:*:*:*:*:*:*
  • linux linux_kernel 2.6.38cpe:2.3:o:linux:linux_kernel:2.6.38:rc8:*:*:*:*:*:*
  • debian debian_linux 11.0cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*