In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix UAF on submount umount iput() called from fuse_release_end() can Oops if the super block has already been destroyed. Normally this is prevented by waiting for num_waiting to go down to zero before commencing with super block shutdown. This only works, however, for the last submount instance, as the wait counter is per connection, not per superblock. Revert to using synchronous release requests for the auto_submounts case, which is virtiofs only at this time.
In the Linux kernel, the following vulnerability has been resolved: virtiofs: fix UAF on submount umount iput() called from fuse_release_end() can Oops if the super block has already been destroyed. Normally this is prevented by waiting for num_waiting to go down to zero before commencing with super block shutdown. This only works, however, for the last submount instance, as the wait counter is per connection, not per superblock. Revert to using synchronous release requests for the auto_submounts case, which is virtiofs only at this time.
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= 548e1f2bac1d4df91a6138f26bb4ab00323fd948 < 607a1d4c42f649e6197567c0448fd9ebb316cd42, >= cfd1aa3e2b71f3327cb373c45a897c9028c62b35 < 1cc0e3a0c6499aaaa2f21a4fcbba388486afb25e, >= 83b375c6efef69b1066ad2d79601221e7892745a < 0b809199ff87c44487e516a725dd4be2185712ce, >= bfd17b6138df0122a95989457d8e18ce0b86165e < 2181a09ba980f142650fb053666350ead4471cfe, >= b26923512dbe57ae4917bafd31396d22a9d1691a < 97c4691653d145dcc699eca5d3aba3219a520f1f, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 2abfd3ffbd9452f72535d96ff3982b3ab1f8f2f9, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 39a2b95e008665c14f84e50ed411d898df7cd11b, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < e09412a714bcd49375198427bb4aa005037a9d6f, >= 26e5c67deb2e1f42a951f022fdf5b9f7eb747b01 < 06b41351779e9289e8785694ade9042ae85e41ea, >= f19a1390af448d9e193c08e28ea5f727bf3c3049, >= 5.10.246 < 5.10.260, >= 5.15.196 < 5.15.211, >= 6.1.158 < 6.1.177, >= 6.6.115 < 6.6.144, >= 6.12.54 < 6.12.95, >= 6.17.4 < 6.18, >= 6.18, >= 6.17.4 < 6.18.37, >= 6.19 < 7.0.14, >= 7.1 < 7.1.2)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.37, 7.0.14, 7.1.2)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 5.10.260, 5.15.211, 6.1.177, 6.6.144, 6.12.95, 6.18.37, 7.0.14, 7.1.2 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
