[v5.15] KASAN: out-of-bounds Write in end_buffer_read_sync

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c957cbb87315 Linux 5.15.105
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17165f59c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=852dc3de44ba1f3f
dashboard link: https://syzkaller.appspot.com/bug?extid=81c6aea085c7a61a49bb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/91d0cf1fc5fb/disk-c957cbb8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/346dc1169521/vmlinux-c957cbb8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f7005bdc0e20/Image-c957cbb8.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+81c6ae...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:101 [inline]
BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:244 [inline]
BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:319 [inline]
BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x3c/0x94 fs/buffer.c:160
Write of size 4 at addr ffff8000270e75c0 by task ksoftirqd/1/20

CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description+0x7c/0x3f0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x174/0x1e4 mm/kasan/report.c:451
kasan_check_range+0x274/0x2b4 mm/kasan/generic.c:189
__kasan_check_write+0x44/0x54 mm/kasan/shadow.c:37
instrument_atomic_read_write include/linux/instrumented.h:101 [inline]
atomic_dec include/linux/atomic/atomic-instrumented.h:244 [inline]
put_bh include/linux/buffer_head.h:319 [inline]
end_buffer_read_sync+0x3c/0x94 fs/buffer.c:160
end_bio_bh_io_sync+0xb0/0x1b4 fs/buffer.c:3007
bio_endio+0x780/0x7c4 block/bio.c:1476
req_bio_endio block/blk-core.c:261 [inline]
blk_update_request+0x5cc/0x134c block/blk-core.c:1440
blk_mq_end_request+0x54/0x88 block/blk-mq.c:575
lo_complete_rq+0x140/0x258 drivers/block/loop.c:529
blk_complete_reqs block/blk-mq.c:587 [inline]
blk_done_softirq+0x11c/0x168 block/blk-mq.c:592
__do_softirq+0x344/0xe20 kernel/softirq.c:558
run_ksoftirqd+0x68/0x258 kernel/softirq.c:920
smpboot_thread_fn+0x4b0/0x920 kernel/smpboot.c:164
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870


Memory state around the buggy address:
ffff8000270e7480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8000270e7500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8000270e7580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
^
ffff8000270e7600: f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f2 f2 f2 f2
ffff8000270e7680: 00 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f48aeeaaa64c Linux 5.15.109
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11718ef8280000
kernel config: https://syzkaller.appspot.com/x/.config?x=bef326567911c94a

dashboard link: https://syzkaller.appspot.com/bug?extid=81c6aea085c7a61a49bb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f4643c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f86f58280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df269bfa2931/disk-f48aeeaa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e64d9fc93268/vmlinux-f48aeeaa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93441fa4b823/Image-f48aeeaa.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d8323b23b189/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+81c6ae...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:101 [inline]
BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:244 [inline]
BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:319 [inline]
BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x3c/0x94 fs/buffer.c:160

Write of size 4 at addr ffff8000234575c0 by task ksoftirqd/0/14

CPU: 0 PID: 14 Comm: ksoftirqd/0 Not tainted 5.15.109-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023

ffff800023457480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff800023457500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff800023457580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
^
ffff800023457600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff800023457680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.