Hello,
syzbot found the following issue on:
HEAD commit: 6139f2a02fe0 Linux 5.15.148
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=151a8ba2180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c170eb20d8be8542
dashboard link:
https://syzkaller.appspot.com/bug?extid=5843ee7d187b36fc6369
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/528e8fe56997/disk-6139f2a0.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/18abf1e442f9/vmlinux-6139f2a0.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/0538a5d3b1f3/bzImage-6139f2a0.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+5843ee...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline]
BUG: KASAN: use-after-free in __mutex_lock_common+0xe4a/0x25a0 kernel/locking/mutex.c:671
Read of size 8 at addr ffff888077d21108 by task jfsCommit/276
CPU: 0 PID: 276 Comm: jfsCommit Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description+0x63/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
__mutex_waiter_is_first kernel/locking/mutex.c:191 [inline]
__mutex_lock_common+0xe4a/0x25a0 kernel/locking/mutex.c:671
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
jfs_syncpt+0x22/0x90 fs/jfs/jfs_logmgr.c:1047
txEnd+0x30b/0x560 fs/jfs/jfs_txnmgr.c:549
txLazyCommit fs/jfs/jfs_txnmgr.c:2718 [inline]
jfs_lazycommit+0x60d/0xc30 fs/jfs/jfs_txnmgr.c:2766
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Allocated by task 12319:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
____kasan_kmalloc+0xba/0xf0 mm/kasan/common.c:513
kasan_kmalloc include/linux/kasan.h:264 [inline]
kmem_cache_alloc_trace+0x143/0x290 mm/slub.c:3247
kmalloc include/linux/slab.h:591 [inline]
kzalloc include/linux/slab.h:721 [inline]
open_inline_log fs/jfs/jfs_logmgr.c:1167 [inline]
lmLogOpen+0x314/0x1030 fs/jfs/jfs_logmgr.c:1077
jfs_mount_rw+0xe3/0x640 fs/jfs/jfs_mount.c:253
jfs_fill_super+0x69f/0xc70 fs/jfs/super.c:570
mount_bdev+0x2c9/0x3f0 fs/super.c:1387
legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1517
do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
Freed by task 3550:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x80 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd8/0x120 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0xdd/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kfree+0xf1/0x270 mm/slub.c:4559
lmLogClose+0x29d/0x530
jfs_umount+0x298/0x370 fs/jfs/jfs_umount.c:116
jfs_put_super+0x86/0x180 fs/jfs/super.c:194
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1414
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
The buggy address belongs to the object at ffff888077d21000
which belongs to the cache kmalloc-1k of size 1024
The buggy address is located 264 bytes inside of
1024-byte region [ffff888077d21000, ffff888077d21400)
The buggy address belongs to the page:
page:ffffea0001df4800 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x77d20
head:ffffea0001df4800 order:3 compound_mapcount:0 compound_pincount:0
flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000010200 dead000000000100 dead000000000122 ffff888011c41dc0
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0x1d2a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL), pid 20, ts 411474402880, free_ts 409676720453
prep_new_page mm/page_alloc.c:2426 [inline]
get_page_from_freelist+0x322a/0x33c0 mm/page_alloc.c:4159
__alloc_pages+0x272/0x700 mm/page_alloc.c:5421
alloc_slab_page mm/slub.c:1775 [inline]
allocate_slab mm/slub.c:1912 [inline]
new_slab+0xbb/0x4b0 mm/slub.c:1975
___slab_alloc+0x6f6/0xe10 mm/slub.c:3008
__slab_alloc mm/slub.c:3095 [inline]
slab_alloc_node mm/slub.c:3186 [inline]
__kmalloc_node_track_caller+0x1f6/0x390 mm/slub.c:4958
kmalloc_reserve net/core/skbuff.c:356 [inline]
pskb_carve_inside_nonlinear net/core/skbuff.c:6306 [inline]
pskb_carve+0x349/0x1bd0 net/core/skbuff.c:6381
pskb_extract+0x4f/0x370 net/core/skbuff.c:6395
rds_tcp_data_recv+0x436/0xa20 net/rds/tcp_recv.c:218
tcp_read_sock+0x279/0xaf0 net/ipv4/tcp.c:1658
rds_tcp_read_sock net/rds/tcp_recv.c:276 [inline]
rds_tcp_data_ready+0x2c4/0x680 net/rds/tcp_recv.c:325
tcp_data_queue+0x2146/0x6f20 net/ipv4/tcp_input.c:5088
tcp_rcv_established+0xe3e/0x1e20 net/ipv4/tcp_input.c:5987
tcp_v6_do_rcv+0x4f2/0x10f0 net/ipv6/tcp_ipv6.c:1526
tcp_v6_rcv+0x2220/0x27b0 net/ipv6/tcp_ipv6.c:1767
ip6_protocol_deliver_rcu+0x93d/0x12d0 net/ipv6/ip6_input.c:425
ip6_input_finish+0xa2/0x130 net/ipv6/ip6_input.c:466
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1340 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0xc34/0xcf0 mm/page_alloc.c:3317
free_unref_page+0x95/0x2d0 mm/page_alloc.c:3396
put_page include/linux/mm.h:1247 [inline]
__skb_frag_unref include/linux/skbuff.h:3219 [inline]
skb_release_data+0x411/0x8a0 net/core/skbuff.c:672
skb_release_all net/core/skbuff.c:742 [inline]
__kfree_skb net/core/skbuff.c:756 [inline]
kfree_skb_reason net/core/skbuff.c:776 [inline]
kfree_skb include/linux/skbuff.h:1123 [inline]
skb_queue_purge+0x1bc/0x2e0 net/core/skbuff.c:3289
rds_tcp_inc_purge net/rds/tcp_recv.c:47 [inline]
rds_tcp_inc_free+0x15/0x30 net/rds/tcp_recv.c:54
rds_tcp_conn_path_shutdown+0x22f/0x2d0 net/rds/tcp_connect.c:221
rds_conn_shutdown+0x4bc/0x960 net/rds/connection.c:398
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Memory state around the buggy address:
ffff888077d21000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888077d21080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888077d21100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888077d21180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888077d21200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup