From: syzbot <syzbot+1afe7ef2d0062e19eeb3@syzkaller.appspotmail.com>
To: jchuang26@m.fudan.edu.cn, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in dbFindLeaf (2)
Date: Mon, 14 Sep 2026 19:03:01 -0700 [thread overview]
Message-ID: <6aa8a755.a211d2ce.1a5198.02a3.GAE@google.com> (raw)
In-Reply-To: <6aa8a1b1.9cc10357.125c5.d000SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: use-after-free Read in copy_folio_from_iter_atomic
==================================================================
BUG: KASAN: use-after-free in memcpy_from_iter lib/iov_iter.c:85 [inline]
BUG: KASAN: use-after-free in iterate_bvec include/linux/iov_iter.h:123 [inline]
BUG: KASAN: use-after-free in iterate_and_advance2 include/linux/iov_iter.h:306 [inline]
BUG: KASAN: use-after-free in iterate_and_advance include/linux/iov_iter.h:330 [inline]
BUG: KASAN: use-after-free in __copy_from_iter lib/iov_iter.c:261 [inline]
BUG: KASAN: use-after-free in copy_folio_from_iter_atomic+0xbbf/0x1a30 lib/iov_iter.c:491
Read of size 4096 at addr ffff88803a53c000 by task kworker/u8:23/3166
CPU: 1 UID: 0 PID: 3166 Comm: kworker/u8:23 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/08/2026
Workqueue: loop0 loop_workfn
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
print_address_description+0x55/0x1e0 mm/kasan/report.c:378
print_report+0x58/0x70 mm/kasan/report.c:482
kasan_report+0x117/0x150 mm/kasan/report.c:595
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x264/0x2c0 mm/kasan/generic.c:200
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
memcpy_from_iter lib/iov_iter.c:85 [inline]
iterate_bvec include/linux/iov_iter.h:123 [inline]
iterate_and_advance2 include/linux/iov_iter.h:306 [inline]
iterate_and_advance include/linux/iov_iter.h:330 [inline]
__copy_from_iter lib/iov_iter.c:261 [inline]
copy_folio_from_iter_atomic+0xbbf/0x1a30 lib/iov_iter.c:491
generic_perform_write+0x5a8/0x8b0 mm/filemap.c:4392
shmem_file_write_iter+0xfb/0x120 mm/shmem.c:3440
lo_rw_aio+0xc78/0xf30 include/linux/percpu-rwsem.h:-1
do_req_filebacked drivers/block/loop.c:430 [inline]
loop_handle_cmd drivers/block/loop.c:1949 [inline]
loop_process_work+0x638/0x11d0 drivers/block/loop.c:1984
process_one_work kernel/workqueue.c:3396 [inline]
process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
worker_thread+0x92d/0xe10 kernel/workqueue.c:3560
kthread+0x38b/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x36 pfn:0x3a53c
flags: 0x80000000000000(node=0|zone=1)
raw: 0080000000000000 ffffea0000c43308 ffffea0001046588 0000000000000000
raw: 0000000000000036 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Unmovable, gfp_mask 0xdc0(GFP_KERNEL|__GFP_ZERO), pid 6669, tgid 6668 (syz.0.55), ts 183365717538
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1f9/0x250 mm/page_alloc.c:1871
prep_new_page mm/page_alloc.c:1879 [inline]
get_page_from_freelist+0x2591/0x2600 mm/page_alloc.c:3943
__alloc_frozen_pages_noprof+0x230/0x5c0 mm/page_alloc.c:5436
alloc_pages_mpol+0xd4/0x280 mm/mempolicy.c:2486
alloc_frozen_pages_noprof mm/mempolicy.c:2557 [inline]
alloc_pages_noprof+0xd2/0x2f0 mm/mempolicy.c:2577
lbmLogInit fs/jfs/jfs_logmgr.c:1813 [inline]
lmLogInit+0x357/0x1a20 fs/jfs/jfs_logmgr.c:1267
open_inline_log fs/jfs/jfs_logmgr.c:1173 [inline]
lmLogOpen+0x4e3/0xf90 fs/jfs/jfs_logmgr.c:1067
jfs_mount_rw+0xf3/0x670 fs/jfs/jfs_mount.c:257
jfs_fill_super+0x769/0xda0 fs/jfs/super.c:533
get_tree_bdev_flags+0x430/0x4f0 fs/super.c:1873
vfs_get_tree+0x92/0x2a0 fs/super.c:1933
fc_mount fs/namespace.c:1198 [inline]
do_new_mount_fc fs/namespace.c:3772 [inline]
do_new_mount+0x319/0xdc0 fs/namespace.c:3848
do_mount fs/namespace.c:4181 [inline]
__do_sys_mount fs/namespace.c:4397 [inline]
__se_sys_mount+0x31d/0x420 fs/namespace.c:4374
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x155/0x510 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
page last free pid 6431 tgid 6431 ts 183464359442 stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
__free_pages_prepare mm/page_alloc.c:1418 [inline]
__free_frozen_pages+0xf3d/0x1000 mm/page_alloc.c:2962
lbmLogShutdown fs/jfs/jfs_logmgr.c:1861 [inline]
lmLogShutdown+0x44e/0x850 fs/jfs/jfs_logmgr.c:1681
lmLogClose+0x28c/0x530 fs/jfs/jfs_logmgr.c:1457
jfs_umount+0x2da/0x3b0 fs/jfs/jfs_umount.c:124
jfs_put_super+0x8c/0x190 fs/jfs/super.c:194
generic_shutdown_super+0x13d/0x2d0 fs/super.c:755
kill_block_super+0x44/0xa0 fs/super.c:1904
deactivate_locked_super+0xbc/0x110 fs/super.c:589
cleanup_mnt+0x3d3/0x460 fs/namespace.c:1317
task_work_run+0x1d9/0x270 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
exit_to_user_mode_loop+0x14e/0x570 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:343 [inline]
do_syscall_64+0x317/0x510 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Memory state around the buggy address:
ffff88803a53bf00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff88803a53bf80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88803a53c000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff88803a53c080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff88803a53c100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
Tested on:
commit: 58785836 Merge tag 'nfsd-7.3-1' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146248c9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a8915f6d5e9da1d8
dashboard link: https://syzkaller.appspot.com/bug?extid=1afe7ef2d0062e19eeb3
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=13ca75f9580000
next parent reply other threads:[~2026-09-15 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aa8a1b1.9cc10357.125c5.d000SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-15 2:03 ` syzbot [this message]
[not found] <6aa7e616.0d1f51e9.2e6de3.473fSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 15:46 ` syzbot
[not found] <177644278876.3785156.11786245630332071250@talencesecurity.com>
2026-04-17 17:17 ` syzbot
[not found] <20260417101153.2489040-1-tristmd@gmail.com>
2026-04-17 10:27 ` syzbot
2026-01-08 13:00 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aa8a755.a211d2ce.1a5198.02a3.GAE@google.com \
--to=syzbot+1afe7ef2d0062e19eeb3@syzkaller.appspotmail.com \
--cc=jchuang26@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®