f2fs: validate MOVE_RANGE destination size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4dd6f977fc778e5a0da604e5f8cb2f36d163d27b · < e533889fc26aea0cd83c90327063f272061dd820| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s f2fs MOVE_RANGE ioctl does not validate the destination end before updating the destination inode’s size. A source hole can cause the operation to succeed while extending the destination inode using an unchecked size. The input does not specify authentication requirements or user interaction.
Engineers running Linux systems that use f2fs should check their kernel versions; affected versions are not specified.