🔍 CVE-2026-97569

0.0
CVSS Score
UNKNOWN
2026-09-25
2026-10-19 10:17
✅ 완료

🇰🇷 한글 설명

Linux 커널의 bnxt_en 드라이버에서 패킷 처리를 지연시키는 과정 중, 특정 조건에서 완료(completion) 신호가 생성되지 않아 네트워크 큐가 멈추는 취약점입니다. 작은 크기의 링 버퍼를 사용하는 환경에서 대량의 패킷과 SW USO 패킷이 결합될 때 발생하며, 이로 인해 큐가 재시작되지 않는 상태에 빠질 수 있습니다.

💡 쉬운 설명

네트워크 카드가 일을 마쳤다는 신호를 보내지 않아 데이터 통로가 영원히 막혀버리는 문제입니다. 특히 네트워크 처리 용량이 작은 설정에서 특정 데이터가 들어올 때 발생할 수 있습니다.

🇺🇸 원문 (English)

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Prevent queue stop with deferred completions When the driver receives a burst of packets, it can mark a BD with the NO_CMPL bit to defer completions. The expectation is that the last packet in the ring will have this bit unset and the completion generated by that packet will cleanup that packet and the ones preceding it. This helps to reduce the number of completions fired. The suppressed completions are controlled by the driver and the number of packets with suppressed completions scales with the size of the ring. SW USO packets, on the other hand, have an upper bound on the maximum number of BDs which can be consumed which does not scale with the ring size. So, for small rings it is possible that: a burst of packets is handed to the driver, the driver defers completions for all of the packets because the number of free descriptors stays above the threshold in the driver. Then, a USO packet arrives, but the number of BDs available is not enough and the USO code exits early. In this case, you end up in a state where the ring is full of packets with their completions suppressed, which can cause the queue to stop and never be restarted. Assuming default CONFIG_MAX_SKB_FRAGS, this is only possible for small rings (<= 457 descriptors, below the driver default value) when a burst of packets fills the ring, followed by a large USO packet that can't fit. For larger rings, the delta between the completion suppression threshold and the BDs required for SW USO is large enough that completions will fire and this case is unreachable. This issue was pointed out by Sashiko and while it seems fairly unlikely given that the queue size must be small to trigger this, it is indeed possible. Fix this by tracking the last BD which deferred completions and centralizing the logic for deciding when to ring the doorbell. The NO_CMPL bit is now cleared in bnxt_txr_db_kick(), so every doorbell site is covered, including the SW USO early exit. This guarantees the ring always ends in a BD which generates a completion to clean it and wake the queue.

📍 영향받는 시스템

Linux kernel (bnxt_en 드라이버를 사용하는 시스템 중 링 크기가 457 디스크립터 이하인 경우)

⚔️ 공격 벡터

특정 크기의 네트워크 패킷 버스트와 SW USO 패킷을 정교하게 조합하여 전송함으로써 네트워크 큐를 중단시킴

🛡️ 대응 방법

Linux 커널을 최신 보안 패치가 적용된 버전으로 업데이트하여 bnxt_txr_db_kick() 로직이 수정된 드라이버를 사용해야 함

🔧 검증 코드

현재 실행 중인 커널 버전을 확인하여 해당 취약점이 해결된 패치 버전인지 확인합니다.

Shell / Script
uname -r

💻 영향받는 소프트웨어

Linux Kernel