f2fs: validate MOVE_RANGE destination size
- 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 6.6.160, 6.12.112, 6.18.53, 7.2.5
- 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 MOVE_RANGE destination size F2FS_IOC_MOVE_RANGE checks the source range, but not the destination end before updating i_size. A source hole can expose this: __clone_blkaddrs() skips NULL_ADDR entries and returns success, so the caller can still extend the destination inode with unchecked pos_out + len. Reject destination overflow and use inode_newsize_ok() before extending the destination inode.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · fixed in 54c587f3f95ce2d6932a16566db83f73cc4313e1; From 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · fixed in bca61ee5192ea47003722486ae9588a2a4bb47b6; From 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · fixed in db13064669526494cd78ba3a4394063b740e940c; From 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · fixed in dcae1eeda53149f219dd6af93b3083b7271c1c63; From 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · fixed in e533889fc26aea0cd83c90327063f272061dd820
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.5