Kestrel
대시보드로 돌아가기
CVE-2024-50164HIGH· 7.1MITRENVD대응게시일: 2024. 11. 07.수정일: 2026. 07. 14.CNA: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Modified

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overloading of MEM_UNINIT's meaning Lonial reported an issue

위협 신호 · CVSS · EPSS · KEV

정기 패치· 높은 악용 신호 없음
CVSS
7.1high

이론적 심각도 점수

EPSS
0.2%상위 89.2%

30일 내 악용 확률 예측

KEV
미등재

실측 악용 기록 없음

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

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

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

CVSS 벡터 · 메트릭

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

상세 설명

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix overloading of MEM_UNINIT's meaning

Lonial reported an issue in the BPF verifier where check_mem_size_reg()
has the following code:

text
1if (!tnum_is_const(reg->var_off))
2 /* For unprivileged variable accesses, disable raw
3 * mode so that the program is required to
4 * initialize all the memory that the helper could
5 * just partially fill up.
6 */
7 meta = NULL;

This means that writes are not checked when the register containing the
size of the passed buffer has not a fixed size. Through this bug, a BPF
program can write to a map which is marked as read-only, for example,
.rodata global maps.

The problem is that MEM_UNINIT's initial meaning that "the passed buffer
to the BPF helper does not need to be initialized" which was added back
in commit 435faee1aae9 ("bpf, verifier: add ARG_PTR_TO_RAW_STACK type")
got overloaded over time with "the passed buffer is being written to".

The problem however is that checks such as the above which were added later
via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta
to NULL in order force the user to always initialize the passed buffer to
the helper. Due to the current double meaning of MEM_UNINIT, this bypasses
verifier write checks to the memory (not boundary checks though) and only
assumes the latter memory is read instead.

Fix this by reverting MEM_UNINIT back to its original meaning, and having
MEM_WRITE as an annotation to BPF helpers in order to then trigger the
BPF verifier checks for writing to memory.

Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO}
we can access fn->arg_type[arg - 1] since it must contain a preceding
ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed
altogether since we do check both BPF_READ and BPF_WRITE. Same for the
equivalent check_kfunc_mem_size_reg().

AI 심층 분석

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

영향받는 제품·버전

  • linux linux_kernel5.19 - 6.6.59
    linux
  • linux linux_kernel6.7 - 6.11.6
    linux
  • linux linux_kernel
    linux
  • linux linux_kernel
    linux
  • linux linux_kernel
    linux
  • linux linux_kernel
    linux

영향받는 구성 (CPE) 5

  • linux linux_kernel≥ 5.19 < 6.6.59cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
  • linux linux_kernel 6.12cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
  • linux linux_kernel 6.12cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
  • linux linux_kernel 6.12cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*
  • linux linux_kernel 6.12cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*