🇰🇷 한글 설명
Linux 커널의 UDP 처리 과정에서 터널링 패킷이 적절한 네트워크 네임스페이스 확인 없이 GRO(Generic Receive Offload)될 때 발생하는 취약점입니다. 이로 인해 패킷 오프셋이 잘못 계산되어 데이터 손상이나 커널 크래시(BUG_ON)가 발생할 수 있습니다.
💡 쉬운 설명
네트워크 데이터를 빠르게 처리하기 위해 여러 패킷을 하나로 묶는 과정에서 오류가 발생하여 컴퓨터 시스템이 멈추거나 데이터가 깨질 수 있는 문제입니다. 특히 특정 네트워크 터널 기술을 사용할 때 시스템이 갑자기 꺼질 위험이 있습니다.
🇺🇸 원문 (English)
In the Linux kernel, the following vulnerability has been resolved:
udp: do not accept non-tunnel GSO skbs landing in a tunnel
When rx-udp-gro-forwarding is enabled UDP packets might be GROed when
being forwarded. If such packets might land in a tunnel this can cause
various issues and udp_gro_receive makes sure this isn't the case by
looking for a matching socket. This is performed in
udp4/6_gro_lookup_skb but only in the current netns. This is an issue
with tunneled packets when the endpoint is in another netns. In such
cases the packets will be GROed at the UDP level, which leads to various
issues later on. The same thing can happen with rx-gro-list.
We saw this with geneve packets being GROed at the UDP level. In such
case gso_size is set; later the packet goes through the geneve rx path,
the geneve header is pulled, the offset are adjusted and frag_list skbs
are not adjusted with regard to geneve. When those skbs hit
skb_fragment, it will misbehave. Different outcomes are possible
depending on what the GROed skbs look like; from corrupted packets to
kernel crashes.
One example is a BUG_ON[1] triggered in skb_segment while processing the
frag_list. Because gso_size is wrong (geneve header was pulled)
skb_segment thinks there is "geneve header size" of data in frag_list,
although it's in fact the next packet. The BUG_ON itself has nothing to
do with the issue. This is only one of the potential issues.
Looking up for a matching socket in udp_gro_receive is fragile: the
lookup could be extended to all netns (not speaking about performances)
but nothing prevents those packets from being modified in between and we
could still not find a matching socket. It's OK to keep the current
logic there as it should cover most cases but we also need to make sure
we handle tunnel packets being GROed too early.
This is done by extending the checks in udp_unexpected_gso: GSO packets
lacking the SKB_GSO_UDP_TUNNEL/_CSUM bits and landing in a tunnel must
be segmented.
[1] kernel BUG at net/core/skbuff.c:4408!
RIP: 0010:skb_segment+0xd2a/0xf70
__udp_gso_segment+0xaa/0x560
📍 영향받는 시스템
Linux Kernel (UDP GRO/GSO 관련 기능이 활성화된 환경)
⚔️ 공격 벡터
특수하게 조작된 UDP 패킷을 전송하여 커널의 GRO 처리 로직을 유도함으로써 시스템 크래시 유발
🛡️ 대응 방법
Linux 커널을 최신 보안 패치가 적용된 버전으로 업데이트
🔧 검증 코드
출력된 커널 버전이 해당 취약점이 수정된 최신 패치 버전인지 확인