CVE-2023-52444

Updated: 2024-03-15 04:59:46.118348

Description:

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]


Links NIST CIRCL RHEL Ubuntu

Severity

Severity Score
CVSS Version 2.x 0
CVSS Version 3.x HIGH 7.8

Status

OS name Project name Version Score Severity Status Errata Last updated
AlmaLinux 9.2 ESU kernel 5.14.0 7.8 HIGH Not Vulnerable 2024-04-09 11:13:40
AlmaLinux 9.2 FIPS kernel 5.14.0 7.8 HIGH Not Vulnerable 2024-04-09 11:13:40
CentOS 8.4 ELS kernel 4.18.0 7.8 HIGH Not Vulnerable 2024-03-20 04:26:25
CentOS 8.5 ELS kernel 4.18.0 7.8 HIGH Not Vulnerable 2024-03-20 04:26:25
Ubuntu 16.04 ELS linux 4.4.0 7.8 HIGH Released CLSA-2024:1710945589 2024-03-20 11:09:29
Ubuntu 16.04 ELS linux-hwe 4.15.0 7.8 HIGH Released CLSA-2024:1710946064 2024-03-20 11:09:32
Ubuntu 18.04 ELS linux 4.15.0 7.8 HIGH Released CLSA-2024:1710946883 2024-03-20 11:09:30