In the Linux kernel, the following vulnerability has been resolved: vsock: Do not allow binding to VMADDR_PORT_ANY It is possible for a vsock to autobind to VMADDR_PORT_ANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDR_PORT_ANY but is not on the list of unbound sockets. Binding it will result in an extra refcount decrement similar to the one fixed in fcdd2242c023 (vsock: Keep the binding until socket destruction). Modify the check in __vsock_bind_connectible() to also prevent binding to VMADDR_PORT_ANY.
In the Linux kernel, the following vulnerability has been resolved: vsock: Do not allow binding to VMADDR_PORT_ANY It is possible for a vsock to autobind to VMADDR_PORT_ANY. This can cause a use-after-free when a connection is made to the bound socket. The socket returned by accept() also has port VMADDR_PORT_ANY but is not on the list of unbound sockets. Binding it will result in an extra refcount decrement similar to the one fixed in fcdd2242c023 (vsock: Keep the binding until socket destruction). Modify the check in __vsock_bind_connectible() to also prevent binding to VMADDR_PORT_ANY.
Linux Linux, linux kernel, debian linux의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel, debian linux >= d021c344051af91f42c5ba9fdedc176740cbd238 < c04a2c1ca25b9b23104124d3b2d349d934e302de, >= d021c344051af91f42c5ba9fdedc176740cbd238 < d1a5b1964cef42727668ac0d8532dae4f8c19386, >= d021c344051af91f42c5ba9fdedc176740cbd238 < cf86704798c1b9c46fa59dfc2d662f57d1394d79, >= d021c344051af91f42c5ba9fdedc176740cbd238 < f138be5d7f301fddad4e65ec66dfc3ceebf79be3, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 44bd006d5c93f6a8f28b106cbae2428c5d0275b7, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 32950b1907919be86a7a2697d6f93d57068b3865, >= d021c344051af91f42c5ba9fdedc176740cbd238 < 8f01093646b49f6330bb2d36761983fd829472b1, >= d021c344051af91f42c5ba9fdedc176740cbd238 < d73960f0cf03ef1dc9e96ec7a20e538accc26d87, >= d021c344051af91f42c5ba9fdedc176740cbd238 < aba0c94f61ec05315fa7815d21aefa4c87f6a9f4, >= 3.9, >= 3.9 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.1.148, >= 6.2 < 6.6.102, >= 6.7 < 6.12.42, >= 6.13 < 6.15.10, >= 6.16 < 6.16.1, 6.17, 11.0)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel, debian linux 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
