f2fs: fix to avoid dirent corruption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in 02160112e6d45c2610b049df6eb693d7a2e57b46; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in 5624a3c1b1ebc8991318e1cce2aa719542991024; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in 6f866885e147d33efc497f1095f35b2ee5ec7310; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in f100ba617d8be6c98a68f3744ef7617082975b77; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in f0145860c20be6bae6785c7a2249577674702ac7; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in d3c0b49aaa12a61d560528f5d605029ab57f0728; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in 2fb4867f4405aea8c0519d7d188207f232a57862; From 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 · fixed in 53edb549565f55ccd0bdf43be3d66ce4c2d48b28
- Linux Linux
4.2
- KernelLinux
From 4.2.0 · fixed in 4.19.306; From 4.20.0 · fixed in 5.4.268; From 5.5.0 · fixed in 5.10.209; From 5.11.0 · fixed in 5.15.148; From 5.16.0 · fixed in 6.1.75; From 6.2.0 · fixed in 6.6.14; From 6.7.0 · fixed in 6.7.2
References 8
git.kernel.org
- stable/c/02160112e6d45c2610b049df6eb693d7a2e57b46
- stable/c/5624a3c1b1ebc8991318e1cce2aa719542991024
- stable/c/6f866885e147d33efc497f1095f35b2ee5ec7310
- stable/c/f100ba617d8be6c98a68f3744ef7617082975b77
- stable/c/f0145860c20be6bae6785c7a2249577674702ac7
- stable/c/d3c0b49aaa12a61d560528f5d605029ab57f0728
- stable/c/2fb4867f4405aea8c0519d7d188207f232a57862
- stable/c/53edb549565f55ccd0bdf43be3d66ce4c2d48b28