[PATCH] f2fs: reject immutable and append-only files in secure trim

From: Hungyu Lin

Date: Thu Nov 19 2026 - 08:09:52 EST


F2FS_IOC_SEC_TRIM_FILE only checks that the file is open for writing. It
does not look at the inode flags, so it discards or zeroes the blocks of
the file even if the file is append-only or immutable.

An append-only file can be opened for writing with O_APPEND, so a user
with write permission on such a file can erase the data that is already
there, which ftruncate() and fallocate() do not allow. For an immutable
file the same works through a file descriptor that was opened for
writing before the flag was set, although f2fs_write_checks() refuses
writes through it.

Return -EPERM if the file is immutable or append-only.

Fixes: 9af846486d78 ("f2fs: add F2FS_IOC_SEC_TRIM_FILE ioctl")
Cc: stable@xxxxxxxxxx
Signed-off-by: Hungyu Lin <dennylin0707@xxxxxxxxx>
---
fs/f2fs/file.c | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index e2c0f5083313..ba131c6f9a54 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -4582,6 +4582,11 @@ static int f2fs_sec_trim_file(struct file *filp, unsigned long arg)
return ret;
inode_lock(inode);

+ if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) {
+ ret = -EPERM;
+ goto err;
+ }
+
if (f2fs_is_atomic_file(inode) || f2fs_compressed_file(inode) ||
range.start >= inode->i_size) {
ret = -EINVAL;
--
2.43.0