First published: Thu Feb 22 2024(Updated: )
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]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=4.2.0<4.19.306 | |
Linux Kernel | >=4.20<5.4.268 | |
Linux Kernel | >=5.5.0<5.10.209 | |
Linux Kernel | >=5.11.0<5.15.148 | |
Linux Kernel | >=5.16.0<6.1.75 | |
Linux Kernel | >=6.2.0<6.6.14 | |
Linux Kernel | >=6.7.0<6.7.2 | |
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-52444 is classified as a medium severity vulnerability affecting the Linux kernel.
To mitigate CVE-2023-52444, upgrade to the latest patched version of the Linux kernel, such as 5.10.223-1 or later.
CVE-2023-52444 affects Linux kernel versions from 4.2.0 up to 6.7.0, excluding patched versions.
The potential impact of CVE-2023-52444 includes possible directory entry corruption in the f2fs filesystem.
All systems running the affected versions of the Linux kernel, especially those using the f2fs filesystem, should prioritize patching for CVE-2023-52444.