In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds read of rtt_min in sock_ops A sockops prog read
위협 신호 · CVSS · EPSS · KEV
이론적 심각도 점수
예측 데이터 없음
실측 악용 기록 없음
계획된 패치 주기 내 조치(60일 이내)
CVSS 벡터 · 메트릭
CVSS 벡터 정보 없음
상세 설명
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix out-of-bounds read of rtt_min in sock_ops
A sockops prog reading skops->rtt_min never checks the sk type: on the
tcp_conn_request() path sock_ops->sk is a request_sock (non-full), and the
ctx rewrite casts it to a tcp_sock (full) and reads rtt_min past the end of
the request_sock, returning dirty adjacent memory.
1SEC("sockops") 2int prog(struct bpf_sock_ops *skops) 3{ 4 switch (skops->op) { 5 case BPF_SOCK_OPS_RWND_INIT: 6 leak = skops->rtt_min; /* reads the request_sock OOB */ 7 ... 8 } 9}For instance one such read returned rtt_min=0xffff8881, the high half of a
leaked kernel pointer.
Guarding that cast is exactly what SOCK_OPS_GET_FIELD() does -- it checks
is_locked_tcp_sock and returns 0 when sock_ops->sk is not a locked full
socket. Every other tcp_sock field in sock_ops goes through it; rtt_min is
the only one open-coded, so it skips the check.
Read rtt_min through SOCK_OPS_GET_FIELD() too. rtt_min is a bit special:
it is a struct minmax and we only want the current min, so pass
rtt_min.s[0].v. That is equivalent to the old hand-computed offset
1offsetof(struct tcp_sock, rtt_min) + sizeof_field(struct minmax_sample, t)(s[0] sits at rtt_min + 0 and .v at + sizeof(.t), i.e. what minmax_get()
returns), so the loaded field is unchanged and only the full-sock guard is
added. The two BUILD_BUG_ON()s that protected the hand-computed offset
are no longer needed.
Before patch:
10: r1 = *(u64 *)(r1 +0) ; r1 = skops->sk 21: r1 = *(u32 *)(r1 +2324) ; ((tcp_sock *)sk)->rtt_min.s[0].vAfter patch:
10: *(u64 *)(r1 +56) = r9 21: r9 = *(u8 *)(r1 +50) ; is_locked_tcp_sock 32: if r9 == 0 goto pc+4 ; not a locked full sock -> 0 43: r9 = *(u64 *)(r1 +56) 54: r1 = *(u64 *)(r1 +0) ; r1 = skops->sk 65: r1 = *(u32 *)(r1 +2324) ; rtt_min.s[0].v 76: goto pc+2 87: r9 = *(u64 *)(r1 +56) 98: r1 = 0AI 심층 분석
공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.
참고 자료 8
링크 내용 불러오는 중…