test

9 views
Skip to first unread message

Manas Ghandat

unread,
Aug 22, 2023, 9:02:01 AM8/22/23
to syzbot+ef50f8...@syzkaller.appspotmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
0001-lmao.patch

syzbot

unread,
Aug 22, 2023, 9:53:29 AM8/22/23
to ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: use-after-free Read in ntfs_attr_find

loop0: detected capacity change from 0 to 4096
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x92c/0xd10 fs/ntfs/attrib.c:601
Read of size 4 at addr ffff8880650dc14c by task syz-executor.0/5458

CPU: 0 PID: 5458 Comm: syz-executor.0 Not tainted 6.5.0-rc6-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0x163/0x540 mm/kasan/report.c:475
kasan_report+0x175/0x1b0 mm/kasan/report.c:588
ntfs_attr_find+0x92c/0xd10 fs/ntfs/attrib.c:601
ntfs_attr_lookup+0x4e4/0x2390
ntfs_read_locked_attr_inode fs/ntfs/inode.c:1239 [inline]
ntfs_attr_iget+0x50a/0x2360 fs/ntfs/inode.c:238
load_system_files+0x1333/0x4840 fs/ntfs/super.c:1808
ntfs_fill_super+0x19b3/0x2bd0 fs/ntfs/super.c:2900
mount_bdev+0x276/0x3b0 fs/super.c:1391
legacy_get_tree+0xef/0x190 fs/fs_context.c:611
vfs_get_tree+0x8c/0x270 fs/super.c:1519
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f83fda7e1ea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f83fe78fee8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f83fe78ff80 RCX: 00007f83fda7e1ea
RDX: 000000002001f6c0 RSI: 000000002001f640 RDI: 00007f83fe78ff40
RBP: 000000002001f6c0 R08: 00007f83fe78ff80 R09: 0000000000008703
R10: 0000000000008703 R11: 0000000000000246 R12: 000000002001f640
R13: 00007f83fe78ff40 R14: 000000000001f621 R15: 000000002001f700
</TASK>

The buggy address belongs to the physical page:
page:ffffea0001943700 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x650dc
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000000 ffffea0001943788 ffffea0001c13248 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), pid 5436, tgid 5436 (dhcpcd-run-hook), ts 81549224797, free_ts 81897816074
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1e6/0x210 mm/page_alloc.c:1570
prep_new_page mm/page_alloc.c:1577 [inline]
get_page_from_freelist+0x31e8/0x3370 mm/page_alloc.c:3221
__alloc_pages+0x255/0x670 mm/page_alloc.c:4477
__folio_alloc+0x13/0x30 mm/page_alloc.c:4509
vma_alloc_folio+0x48a/0x9a0 mm/mempolicy.c:2253
do_anonymous_page mm/memory.c:4104 [inline]
do_pte_missing mm/memory.c:3662 [inline]
handle_pte_fault mm/memory.c:4939 [inline]
__handle_mm_fault mm/memory.c:5079 [inline]
handle_mm_fault+0x20c7/0x5410 mm/memory.c:5233
do_user_addr_fault arch/x86/mm/fault.c:1343 [inline]
handle_page_fault arch/x86/mm/fault.c:1486 [inline]
exc_page_fault+0x3cf/0x7c0 arch/x86/mm/fault.c:1542
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1161 [inline]
free_unref_page_prepare+0x903/0xa30 mm/page_alloc.c:2348
free_unref_page_list+0x596/0x830 mm/page_alloc.c:2489
release_pages+0x2193/0x2470 mm/swap.c:1042
tlb_batch_pages_flush mm/mmu_gather.c:97 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:292 [inline]
tlb_flush_mmu+0x100/0x210 mm/mmu_gather.c:299
tlb_finish_mmu+0xd4/0x1f0 mm/mmu_gather.c:391
exit_mmap+0x3e2/0xad0 mm/mmap.c:3215
__mmput+0x115/0x3c0 kernel/fork.c:1348
exit_mm+0x21f/0x300 kernel/exit.c:567
do_exit+0x612/0x2290 kernel/exit.c:861
do_group_exit+0x206/0x2c0 kernel/exit.c:1024
__do_sys_exit_group kernel/exit.c:1035 [inline]
__se_sys_exit_group kernel/exit.c:1033 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1033
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
ffff8880650dc000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff8880650dc080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff8880650dc100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff8880650dc180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff8880650dc200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


Tested on:

commit: 2ccdd1b1 Linux 6.5-rc6
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.5-rc6
console output: https://syzkaller.appspot.com/x/log.txt?x=1012c769a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c37cc0e4fcc5f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=ef50f8eb00b54feb7ba2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12eaf76ba80000

Manas Ghandat

unread,
Aug 26, 2023, 1:33:38 PM8/26/23
to syzbot+91ad2b...@syzkaller.appspotmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
0001-jfs-fix-shift-out-of-bounds-in-dbUpdatePMap.patch

syzbot

unread,
Aug 26, 2023, 1:33:39 PM8/26/23
to ghanda...@gmail.com, ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
> #syz test:

want 2 args (repo, branch), got 1

> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.4-rc5

Manas Ghandat

unread,
Aug 26, 2023, 1:36:22 PM8/26/23
to syzkall...@googlegroups.com, syzk...@googlegroups.com, syzbot+91ad2b...@syzkaller.appspotmail.com
0001-jfs-fix-shift-out-of-bounds-in-dbUpdatePMap.patch

syzbot

unread,
Aug 26, 2023, 2:13:27 PM8/26/23
to ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+91ad2b...@syzkaller.appspotmail.com

Tested on:

commit: 9561de3a Linux 6.4-rc5
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.4-rc5
console output: https://syzkaller.appspot.com/x/log.txt?x=17e77affa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2edcdd2db48bb6d1
dashboard link: https://syzkaller.appspot.com/bug?extid=91ad2b52815a08caf4ea
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10483c87a80000

Note: testing is done by a robot and is best-effort only.

Manas Ghandat

unread,
Aug 30, 2023, 4:34:59 AM8/30/23
to syzbot, syzk...@googlegroups.com, syzkall...@googlegroups.com

syzbot

unread,
Aug 30, 2023, 7:46:33 AM8/30/23
to ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+91ad2b...@syzkaller.appspotmail.com

Tested on:

commit: 2dde18cd Linux 6.5
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v6.5
console output: https://syzkaller.appspot.com/x/log.txt?x=12de3f18680000
kernel config: https://syzkaller.appspot.com/x/.config?x=53a11bb362404263
dashboard link: https://syzkaller.appspot.com/bug?extid=91ad2b52815a08caf4ea
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.

Manas Ghandat

unread,
Sep 6, 2023, 9:56:07 PM9/6/23
to syzbot+0558d1...@syzkaller.appspotmail.com, syzk...@googlegroups.com, syzkall...@googlegroups.com

syzbot

unread,
Sep 6, 2023, 10:09:38 PM9/6/23
to ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: array-index-out-of-bounds in txCommit

================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_txnmgr.c:1743:5
index 18 is out of range for type 'xad_t[18]' (aka 'struct xad[18]')
CPU: 0 PID: 5458 Comm: syz-executor.0 Not tainted 6.5.0-syzkaller-12107-g7ba2090ca64e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:217 [inline]
__ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348
xtLog fs/jfs/jfs_txnmgr.c:1743 [inline]
txLog fs/jfs/jfs_txnmgr.c:1396 [inline]
txCommit+0x3f0b/0x6ba0 fs/jfs/jfs_txnmgr.c:1264
jfs_commit_inode+0x366/0x580 fs/jfs/inode.c:108
extAlloc+0xcac/0x1000 fs/jfs/jfs_extent.c:172
jfs_get_block+0x41b/0xe60 fs/jfs/inode.c:248
__block_write_begin_int+0x555/0x1a40 fs/buffer.c:2107
__block_write_begin fs/buffer.c:2157 [inline]
block_write_begin+0x9b/0x1e0 fs/buffer.c:2216
jfs_write_begin+0x31/0x70 fs/jfs/inode.c:299
generic_perform_write+0x31b/0x630 mm/filemap.c:3942
__generic_file_write_iter+0x1b4/0x230 mm/filemap.c:4034
generic_file_write_iter+0xaf/0x310 mm/filemap.c:4063
do_iter_write+0x84f/0xde0 fs/read_write.c:860
iter_file_splice_write+0x86d/0x1010 fs/splice.c:736
do_splice_from fs/splice.c:933 [inline]
direct_splice_actor+0xea/0x1c0 fs/splice.c:1142
splice_direct_to_actor+0x376/0x9e0 fs/splice.c:1088
do_splice_direct+0x2ac/0x3f0 fs/splice.c:1194
do_sendfile+0x623/0x1070 fs/read_write.c:1254
__do_sys_sendfile64 fs/read_write.c:1322 [inline]
__se_sys_sendfile64+0x17c/0x1e0 fs/read_write.c:1308
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff664c7cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff665a240c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007ff664d9bf80 RCX: 00007ff664c7cae9
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000008
RBP: 00007ff664cc847a R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201004 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007ff664d9bf80 R15: 00007ffd96b083d8
</TASK>
================================================================================


Tested on:

commit: 7ba2090c Merge tag 'ceph-for-6.6-rc1' of https://githu..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=11680480680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3078d4e429da4c39
dashboard link: https://syzkaller.appspot.com/bug?extid=0558d19c373e44da3c18

Manas Ghandat

unread,
Sep 7, 2023, 12:59:43 PM9/7/23
to syzbot+38e876...@syzkaller.appspotmail.com, syzk...@googlegroups.com, syzkall...@googlegroups.com

syzbot

unread,
Sep 7, 2023, 1:22:35 PM9/7/23
to ghanda...@gmail.com, syzkall...@googlegroups.com, syzk...@googlegroups.com
Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: array-index-out-of-bounds in dbNextAG

loop0: detected capacity change from 0 to 32768
================================================================================
UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:640:20
index 7936 is out of range for type 'atomic_t[128]'
CPU: 0 PID: 5466 Comm: syz-executor.0 Not tainted 6.5.0-syzkaller-12107-g7ba2090ca64e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:217 [inline]
__ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348
dbNextAG+0x600/0x630 fs/jfs/jfs_dmap.c:640
dbAlloc+0x62d/0xca0 fs/jfs/jfs_dmap.c:875
dtSplitUp fs/jfs/jfs_dtree.c:974 [inline]
dtInsert+0xda7/0x6b00 fs/jfs/jfs_dtree.c:863
jfs_symlink+0x824/0x10d0 fs/jfs/namei.c:1019
vfs_symlink+0x12f/0x2a0 fs/namei.c:4480
do_symlinkat+0x201/0x610 fs/namei.c:4506
__do_sys_symlink fs/namei.c:4527 [inline]
__se_sys_symlink fs/namei.c:4525 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4525
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe1bfa7cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fe1c07050c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007fe1bfb9bf80 RCX: 00007fe1bfa7cae9
RDX: 0000000000000000 RSI: 0000000020000880 RDI: 0000000020001980
RBP: 00007fe1bfac847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe1bfb9bf80 R15: 00007fff5037e208
</TASK>
================================================================================


Tested on:

commit: 7ba2090c Merge tag 'ceph-for-6.6-rc1' of https://githu..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=17ff6f10680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3078d4e429da4c39
dashboard link: https://syzkaller.appspot.com/bug?extid=38e876a8aa44b7115c76
Reply all
Reply to author
Forward
0 new messages