f2fs: validate orphan inode entry count
- 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
- 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
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.8
References 8
git.kernel.org
- stable/c/210c210c92d78fdf5051bc55c5c69044b1a2150a
- stable/c/ad101d15716f5a24d1fa82a849f80430c805a3dd
- stable/c/d18c81f5d0ecd5796aa47d66d98f2dd54d8d0f70
- stable/c/d2f236196d542ccd8505736e41c3a1d3f0305f6f
- stable/c/550511a2470f6d204fa07b331f048bd2d3c51280
- stable/c/8aad54746c251f2c2370118df766c0c82e2d2091
- stable/c/2e12381d4495dc8b0ff042c6856022b2e359835c
- stable/c/846c499a65816d13f1186e3090e825e8bb8bcb8b