f2fs: validate compress cache inode only when enabled
- 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 5.14
- 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 compress cache inode only when enabled F2FS_COMPRESS_INO() uses NM_I(sbi)->max_nid as the synthetic inode number for the compressed page cache inode. That inode only exists when the compress_cache mount option is enabled. When compress_cache is disabled, max_nid is outside the valid inode range. A corrupted directory entry that points to ino == max_nid should therefore be rejected by f2fs_check_nid_range(). However, is_meta_ino() currently treats F2FS_COMPRESS_INO() as a meta inode unconditionally, so f2fs_iget() bypasses do_read_inode() and its nid range check, and instantiates a fake internal inode instead. Gate the compressed cache inode case on COMPRESS_CACHE, matching f2fs_init_compress_inode(). With compress_cache disabled, ino == max_nid now follows the normal inode path and is rejected as an out-of-range nid.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5.13.19 · fixed in 5.14
- Linux Linux
5.14
References 7
git.kernel.org
- stable/c/fcc051d377a9701a452e7663a1a8223c26225df9
- stable/c/29115b8c9172d34e67ab26cc4f6c209b7a236d7a
- stable/c/13e4b59d3a9413f66f116fa6c4828519b960a5ea
- stable/c/16161444c30d8dff9428abbae42b72ce4e32a932
- stable/c/77f216ff9ce5cde8eed9f6d12707e906dffdc9f7
- stable/c/0969926d987bbde9a1aa49da317582ba37095805
- stable/c/5073c66a96a9c23c0c2533ed4ed06e42f9021208