In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid dirent corruption As Al reported in link[1]: f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0); You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place. [1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/ With below testcase, it may cause dirent corruption, due to it missed to call...
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid dirent corruption As Al reported in link[1]: f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0); You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place. [1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/ With below testcase, it may cause dirent corruption, due to it missed to call...
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 02160112e6d45c2610b049df6eb693d7a2e57b46, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 5624a3c1b1ebc8991318e1cce2aa719542991024, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 6f866885e147d33efc497f1095f35b2ee5ec7310, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < f100ba617d8be6c98a68f3744ef7617082975b77, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < f0145860c20be6bae6785c7a2249577674702ac7, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < d3c0b49aaa12a61d560528f5d605029ab57f0728, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 2fb4867f4405aea8c0519d7d188207f232a57862, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 53edb549565f55ccd0bdf43be3d66ce4c2d48b28, >= 4.2, >= 4.2.0 < 4.19.306, >= 4.20 < 5.4.268, >= 5.5.0 < 5.10.209, >= 5.11.0 < 5.15.148, >= 5.16.0 < 6.1.75, >= 6.2.0 < 6.6.14, >= 6.7.0 < 6.7.2)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
