In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however...
In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however...
Linux Linux, linux kernel, debian linux의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel, debian linux >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a514fca2b8e95838a3ba600f31a18fa60b76d893, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < ac6992f72bd8e22679c1e147ac214de6a7093c23, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < dc7722619a9c307e9938d735cf4a2210d3d48dcb, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a8acc7080ad55c5402a1b818b3008998247dda87, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 55c3dbd8389636161090a2b2b6d2d709b9602e9c, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < e9799db771b2d574d5bf0dfb3177485e5f40d4d6, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < fc27ab48904ceb7e4792f0c400f1ef175edf16fe, >= 4.2, >= 4.2 < 5.4.295, >= 5.5 < 5.10.239, >= 5.11 < 5.15.186, >= 5.16 < 6.1.142, >= 6.2 < 6.6.95, >= 6.7 < 6.12.35, >= 6.13 < 6.15.4, 6.16, 11.0)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel, debian linux 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4 기준을 충족하는지 확인합니다. 이어서 유형 미확정 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
