In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no...
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no...
Linux Linux, linux kernel, debian linux의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel, debian linux >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 03dcdd2558e1e55bf843822fe4363dcb48743f2b, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 15a6f4971e2f157d57e09ea748d1fbc714277aa4, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < dab8ded2e5ff41012a6ff400b44dbe76ccf3592a, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 1dbf7cd2454a28b1da700085b99346b5445aeabb, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < be4b8392da7978294f2f368799d29dd509fb6c4d, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 50aa2d121bc2cfe2d825f8a331ea75dfaaab6a50, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 3b89e17b2fd64012682bed158d9eb3d2e96dec42, >= c5fa7b3cf3cb22e4ac60485fc2dc187fe012910f < 667eeab4999e981c96b447a4df5f20bdf5c26f13, >= 3.11, >= 3.11 < 5.4.296, >= 5.5 < 5.10.240, >= 5.11 < 5.15.189, >= 5.16 < 6.1.146, >= 6.2 < 6.6.99, >= 6.7 < 6.12.39, >= 6.13 < 6.15.7, 6.16, 11.0)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel, debian linux 5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
