f2fs: validate orphan inode entry count
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 127e670abfa7fa150f6550d620ded930f5bdb4e7 · < 8aad54746c251f2c2370118df766c0c82e2d2091| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: validate orphan inode entry count
f2fs_recover_orphan_inodes() trusts the orphan block entry_count when replaying orphan inodes from the checkpoint pack. A corrupted entry_count larger than F2FS_ORPHANS_PER_BLOCK makes the recovery loop read past the ino[] array and interpret footer or following data as inode numbers.
On a crafted image, mounting an unpatched kernel can drive orphan recovery into f2fs_bug_on() and panic the kernel. Validate entry_count before consuming entries so corrupted checkpoint data fails the mount with -EFSCORRUPTED and requests fsck instead.
Set ERROR_INCONSISTENT_ORPHAN as well, so the corruption reason can be recorded in the superblock s_errors[] field. This gives fsck a persistent hint even though mount-time orphan recovery failure may leave no chance to persist SBI_NEED_FSCK through a checkpoint.
From the CVE record · Linux
The Linux kernel’s f2fs orphan recovery trusts an entry count in a checkpoint block, allowing an out-of-bounds read. Mounting a crafted filesystem image on an unpatched kernel can trigger a kernel panic; the described attack requires the image to be mounted.
Engineers running Linux kernels with f2fs support should check their installations; affected versions are not specified.