Review reviewHigh

CVE-2023-52444

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.24%
15.7% percentile
CISA KEV
Not listed
Published
2024.02.23
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.24%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 02160112e6d45c2610b049df6eb693d7a2e57b46, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 5624a3c1b1ebc8991318e1cce2aa719542991024, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 6f866885e147d33efc497f1095f35b2ee5ec7310, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < f100ba617d8be6c98a68f3744ef7617082975b77, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < f0145860c20be6bae6785c7a2249577674702ac7, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < d3c0b49aaa12a61d560528f5d605029ab57f0728, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 2fb4867f4405aea8c0519d7d188207f232a57862, >= 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 < 53edb549565f55ccd0bdf43be3d66ce4c2d48b28, >= 4.2, >= 4.2.0 < 4.19.306, >= 4.20 < 5.4.268, >= 5.5.0 < 5.10.209, >= 5.11.0 < 5.15.148, >= 5.16.0 < 6.1.75, >= 6.2.0 < 6.6.14, >= 6.7.0 < 6.7.2
Fixed versions
4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-119