Answer in brief
CVE-2023-52444 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to avoid dirent corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-52444 records a High severity (CVSS 7.8) vulnerability in f2fs: fix to avoid dirent corruption. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <02160112e6d45c2610b049df6eb693d7a2e57b46 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <5624a3c1b1ebc8991318e1cce2aa719542991024 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <6f866885e147d33efc497f1095f35b2ee5ec7310 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f100ba617d8be6c98a68f3744ef7617082975b77 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f0145860c20be6bae6785c7a2249577674702ac7 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <d3c0b49aaa12a61d560528f5d605029ab57f0728 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <2fb4867f4405aea8c0519d7d188207f232a57862 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <53edb549565f55ccd0bdf43be3d66ce4c2d48b28 | 02160112e6d45c2610b049df6eb693d7a2e57b46, 5624a3c1b1ebc8991318e1cce2aa719542991024, 6f866885e147d33efc497f1095f35b2ee5ec7310, f100ba617d8be6c98a68f3744ef7617082975b77, f0145860c20be6bae6785c7a2249577674702ac7, d3c0b49aaa12a61d560528f5d605029ab57f0728, 2fb4867f4405aea8c0519d7d188207f232a57862, 53edb549565f55ccd0bdf43be3d66ce4c2d48b28 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Feb 22, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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]
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <02160112e6d45c2610b049df6eb693d7a2e57b46 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <5624a3c1b1ebc8991318e1cce2aa719542991024 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <6f866885e147d33efc497f1095f35b2ee5ec7310 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f100ba617d8be6c98a68f3744ef7617082975b77 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f0145860c20be6bae6785c7a2249577674702ac7 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <d3c0b49aaa12a61d560528f5d605029ab57f0728 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <2fb4867f4405aea8c0519d7d188207f232a57862 || >=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <53edb549565f55ccd0bdf43be3d66ce4c2d48b28 | 02160112e6d45c2610b049df6eb693d7a2e57b46, 5624a3c1b1ebc8991318e1cce2aa719542991024, 6f866885e147d33efc497f1095f35b2ee5ec7310, f100ba617d8be6c98a68f3744ef7617082975b77, f0145860c20be6bae6785c7a2249577674702ac7, d3c0b49aaa12a61d560528f5d605029ab57f0728, 2fb4867f4405aea8c0519d7d188207f232a57862, 53edb549565f55ccd0bdf43be3d66ce4c2d48b28 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Feb 22, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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]
Quoted source text, attributed separately from HOL analysis.