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 f2fs_set_link() to update ".." link to new directory. - mkdir -p dir/foo - renameat2 -w dir/foo bar [ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs [Fail]
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: Linux

Published: 2024-02-22T16:21:37.043Z

Updated: 2024-07-05T17:21:03.571Z

Reserved: 2024-02-20T12:30:33.291Z


Link: CVE-2023-52444

JSON object: View

cve-icon NVD Information

Status : Modified

Published: 2024-02-22T17:15:08.430

Modified: 2024-06-27T12:15:14.353


Link: CVE-2023-52444

JSON object: View

cve-icon Redhat Information

No data.

CWE