🇰🇷 한글 설명
Linux 커널의 ksmbd 서버에서 연결 할당 실패 시 active_num_conn 카운터가 감소하지 않는 메모리 누수 취약점이 발견되었습니다. 공격자가 의도적으로 할당 실패를 유도할 경우, 최대 연결 제한에 도달하여 서버가 모든 새로운 연결을 거부하는 서비스 거부(DoS) 상태에 빠질 수 있습니다.
💡 쉬운 설명
서버에 연결을 시도하다가 오류가 발생했을 때, 사용 중인 연결 숫자를 제대로 줄이지 않는 버그가 있습니다. 이 버그를 이용해 가짜 연결을 계속 만들면 서버가 '연결 가능한 인원이 꽉 찼다'고 착각하여 실제 사용자의 접속을 모두 차단하게 됩니다.
🇺🇸 원문 (English)
In the Linux kernel, the following vulnerability has been resolved:
smb: server: fix active_num_conn leak on transport allocation failure
Commit 77ffbcac4e56 ("smb: server: fix leak of active_num_conn in
ksmbd_tcp_new_connection()") addressed the kthread_run() failure
path. The earlier alloc_transport() == NULL path in the same
function has the same leak, is reachable pre-authentication via any
TCP connect to port 445, and was empirically reproduced on UML
(ARCH=um, v7.0-rc7): a small number of forced allocation failures
were sufficient to put ksmbd into a state where every subsequent
connection attempt was rejected for the remainder of the boot.
ksmbd_kthread_fn() increments active_num_conn before calling
ksmbd_tcp_new_connection() and discards the return value, so when
alloc_transport() returns NULL the socket is released and -ENOMEM
returned without decrementing the counter. Each such failure
permanently consumes one slot from the max_connections pool; once
cumulative failures reach the cap, atomic_inc_return() hits the
threshold on every subsequent accept and every new connection is
rejected. The counter is only reset by module reload.
An unauthenticated remote attacker can drive the server toward the
memory pressure that makes alloc_transport() fail by holding open
connections with large RFC1002 lengths up to MAX_STREAM_PROT_LEN
(0x00FFFFFF); natural transient allocation failures on a loaded
host produce the same drift more slowly.
Mirror the existing rollback pattern in ksmbd_kthread_fn(): on the
alloc_transport() failure path, decrement active_num_conn gated on
server_conf.max_connections.
Repro details: with the patch reverted, forced alloc_transport()
NULL returns leaked counter slots and subsequent connection
attempts -- including legitimate connects issued after the
forced-fail window had closed -- were all rejected with "Limit the
maximum number of connections". With this patch applied, the same
connect sequence produces no rejections and the counter cycles
cleanly between zero and one on every accept.
📍 영향받는 시스템
Linux kernel (ksmbd module 사용 환경)
⚔️ 공격 벡터
인증되지 않은 원격 공격자가 445번 포트로 대량의 TCP 연결을 시도하여 메모리 할당 실패를 유도함
🛡️ 대응 방법
커널 패치(Commit 77ffbcac4e56)를 적용하거나 ksmbd 모듈을 최신 버전으로 업데이트함
🔧 검증 코드
현재 실행 중인 커널 버전과 ksmbd 모듈 정보를 확인하여 패치 적용 여부를 검토합니다.
uname -r && modinfo ksmbd | grep -i version