linux-kernel - [PATCH v3 2/2] bfs: ensure buffer is marked uptodate before marking it dirty

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240822161219.459054-3-kovalev@altlinux.org>
Date: Thu, 22 Aug 2024 19:12:19 +0300
From: kovalev@...linux.org
To: linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	aivazian.tigran@...il.com,
	stable@...r.kernel.org
Cc: lvc-patches@...uxtesting.org,
	dutyrok@...linux.org,
	kovalev@...linux.org,
	syzbot+d98fd19acd08b36ff422@...kaller.appspotmail.com
Subject: [PATCH v3 2/2] bfs: ensure buffer is marked uptodate before marking it dirty

From: Vasiliy Kovalev <kovalev@...linux.org>

Add a call to `set_buffer_uptodate(new)` in `bfs_move_block` before
marking the buffer as dirty. This change ensures the buffer is correctly
flagged as containing valid data after copying, preventing potential data
inconsistencies or corruption during writeback.

Found by Syzkaller:

WARNING: CPU: 1 PID: 5055 at fs/buffer.c:1176 mark_buffer_dirty+0x37b/0x3f0 fs/buffer.c:1176
Modules linked in:
CPU: 1 PID: 5055 Comm: syz-executor162 Not tainted 6.8.0-rc1-syzkaller-00049-g6098d87eaf31 #0
Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:mark_buffer_dirty+0x37b/0x3f0 fs/buffer.c:1176
Call Trace:

 bfs_move_block fs/bfs/file.c:44 [inline]
 bfs_move_blocks fs/bfs/file.c:57 [inline]
 bfs_get_block+0x3e5/0xeb0 fs/bfs/file.c:126
 __block_write_begin_int+0x4fb/0x16e0 fs/buffer.c:2103
 __block_write_begin fs/buffer.c:2152 [inline]
 block_write_begin+0xb1/0x490 fs/buffer.c:2211
 bfs_write_begin+0x31/0xd0 fs/bfs/file.c:179
 generic_perform_write+0x278/0x600 mm/filemap.c:3930
 __generic_file_write_iter+0x1f9/0x240 mm/filemap.c:4025
 generic_file_write_iter+0xe3/0x350 mm/filemap.c:4051
 call_write_iter include/linux/fs.h:2085 [inline]
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0x6d5/0x1100 fs/read_write.c:590
 ksys_write+0x12f/0x250 fs/read_write.c:643
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Reported-by: syzbot+d98fd19acd08b36ff422@...kaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d98fd19acd08b36ff422
Cc: stable@...r.kernel.org
Signed-off-by: Vasiliy Kovalev <kovalev@...linux.org>
---
 fs/bfs/file.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/bfs/file.c b/fs/bfs/file.c
index 23773e62994024..3f0c506584560e 100644
--- a/fs/bfs/file.c
+++ b/fs/bfs/file.c
@@ -44,6 +44,7 @@ static int bfs_move_block(unsigned long from, unsigned long to,
 		return -EIO;
 	}
 	memcpy(new->b_data, bh->b_data, bh->b_size);
+	set_buffer_uptodate(new);
 	mark_buffer_dirty(new);
 	bforget(bh);
 	brelse(new);
-- 
2.33.8