CVE-2023-52444: f2fs: fix to avoid dirent corruption
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid dirent corruption
As Al reported in link[1]:
f2fsrename() ... if (olddir != newdir && !whiteout) f2fssetlink(oldinode, olddirentry, olddirpage, newdir); else f2fsputpage(olddirpage, 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 f2fssetlink() to update ".." link to new directory. - mkdir -p dir/foo - renameat2 -w dir/foo bar
[ASSERT] (chkdotsdentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs [Fail]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52444?
CVE-2023-52444 is classified as a medium severity vulnerability affecting the Linux kernel.
How do I fix CVE-2023-52444?
To mitigate CVE-2023-52444, upgrade to the latest patched version of the Linux kernel, such as 5.10.223-1 or later.
Which versions of the Linux kernel are affected by CVE-2023-52444?
CVE-2023-52444 affects Linux kernel versions from 4.2.0 up to 6.7.0, excluding patched versions.
What is the potential impact of CVE-2023-52444?
The potential impact of CVE-2023-52444 includes possible directory entry corruption in the f2fs filesystem.
Which systems should prioritize patching for CVE-2023-52444?
All systems running the affected versions of the Linux kernel, especially those using the f2fs filesystem, should prioritize patching for CVE-2023-52444.