[Android 5.15] KASAN: use-after-free Read in rcu_cblist_dequeue

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c85054db4618 Merge 64ee49df839f ("s390/xor: Fix xor_xc_2()..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=11801fae580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30048ef22650d7ee
dashboard link: https://syzkaller.appspot.com/bug?extid=2e15c1bc88c41a37e619
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1172f4ea580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165900d6580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c74b28885c5a/disk-c85054db.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09d149ced009/vmlinux-c85054db.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a0fb16f3ab0e/bzImage-c85054db.xz

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

==================================================================
BUG: KASAN: use-after-free in rcu_cblist_dequeue+0x6c/0xb0 kernel/rcu/rcu_segcblist.c:75
Read of size 8 at addr ffff8881103a1190 by task ksoftirqd/1/25

CPU: 1 PID: 25 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
<TASK>
__dump_stack+0x21/0x30 lib/dump_stack.c:88
dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
print_address_description+0x7f/0x2c0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:427 [inline]
kasan_report+0x10f/0x150 mm/kasan/report.c:444
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report_generic.c:309
rcu_cblist_dequeue+0x6c/0xb0 kernel/rcu/rcu_segcblist.c:75
rcu_do_batch+0x47d/0xbf0 kernel/rcu/tree.c:2512
rcu_core+0x4a3/0xef0 kernel/rcu/tree.c:2763
rcu_core_si+0x9/0x10 kernel/rcu/tree.c:2776
handle_softirqs+0x250/0x560 kernel/softirq.c:583
run_ksoftirqd+0x28/0x40 kernel/softirq.c:959
smpboot_thread_fn+0x446/0x880 kernel/smpboot.c:164
kthread+0x3f5/0x4f0 kernel/kthread.c:337
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>

Allocated by task 372:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:45 [inline]
set_alloc_info mm/kasan/common.c:433 [inline]
____kasan_kmalloc mm/kasan/common.c:512 [inline]
__kasan_kmalloc+0xd4/0x100 mm/kasan/common.c:521
kasan_kmalloc include/linux/kasan.h:227 [inline]
__kmalloc+0x13d/0x2c0 mm/slub.c:4436
kmalloc include/linux/slab.h:624 [inline]
kzalloc include/linux/slab.h:750 [inline]
l2tp_session_create+0x39/0xb60 net/l2tp/l2tp_core.c:1616
pppol2tp_connect+0xbf5/0x1640 net/l2tp/l2tp_ppp.c:772
__sys_connect_file net/socket.c:1922 [inline]
__sys_connect+0x3cb/0x450 net/socket.c:1939
__do_sys_connect net/socket.c:1949 [inline]
__se_sys_connect net/socket.c:1946 [inline]
__x64_sys_connect+0x7a/0x90 net/socket.c:1946
x64_sys_call+0x7c/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:43
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

Freed by task 312:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4a/0x70 mm/kasan/common.c:45
kasan_set_free_info+0x23/0x40 mm/kasan/generic.c:370
____kasan_slab_free+0x125/0x160 mm/kasan/common.c:365
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:373
kasan_slab_free include/linux/kasan.h:193 [inline]
slab_free_hook mm/slub.c:1728 [inline]
slab_free_freelist_hook+0xc2/0x190 mm/slub.c:1754
slab_free mm/slub.c:3526 [inline]
kfree+0xc4/0x270 mm/slub.c:4588
l2tp_session_free net/l2tp/l2tp_core.c:168 [inline]
l2tp_session_put+0xaf/0x1a0 net/l2tp/l2tp_core.c:193
l2tp_session_delete+0x3a9/0x4a0 net/l2tp/l2tp_core.c:1589
l2tp_tunnel_closeall net/l2tp/l2tp_core.c:1235 [inline]
l2tp_tunnel_del_work+0x180/0x3d0 net/l2tp/l2tp_core.c:1273
process_one_work+0x6c8/0xbb0 kernel/workqueue.c:2328
worker_thread+0xaa0/0x1250 kernel/workqueue.c:2475
kthread+0x3f5/0x4f0 kernel/kthread.c:337
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

Last potentially related work creation:
kasan_save_stack+0x3a/0x60 mm/kasan/common.c:38
__kasan_record_aux_stack+0xd2/0x100 mm/kasan/generic.c:348
kasan_record_aux_stack_noalloc+0xb/0x10 mm/kasan/generic.c:358
__call_rcu_common kernel/rcu/tree.c:3011 [inline]
call_rcu+0x10b/0xf60 kernel/rcu/tree.c:3129
pppol2tp_release+0x1e3/0x2b0 net/l2tp/l2tp_ppp.c:447
__sock_release net/socket.c:649 [inline]
sock_close+0xb8/0x200 net/socket.c:1335
__fput+0x22b/0x900 fs/file_table.c:311
____fput+0x15/0x20 fs/file_table.c:339
task_work_run+0x127/0x190 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0xd0/0xe0 kernel/entry/common.c:181
exit_to_user_mode_prepare+0x87/0xd0 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0

The buggy address belongs to the object at ffff8881103a1000
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 400 bytes inside of
512-byte region [ffff8881103a1000, ffff8881103a1200)
The buggy address belongs to the page:
page:ffffea000440e800 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1103a0
head:ffffea000440e800 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x4000000000010200(slab|head|zone=1)
raw: 4000000000010200 dead000000000100 dead000000000122 ffff888100042f00
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 2, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 108, ts 3765815759, free_ts 0
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x192/0x1b0 mm/page_alloc.c:2607
prep_new_page+0x1c/0x110 mm/page_alloc.c:2613
get_page_from_freelist+0x2c3a/0x2cd0 mm/page_alloc.c:4487
__alloc_pages+0x1a2/0x460 mm/page_alloc.c:5824
alloc_slab_page mm/slub.c:-1 [inline]
allocate_slab mm/slub.c:1937 [inline]
new_slab+0xa0/0x4d0 mm/slub.c:2000
___slab_alloc+0x3ac/0x840 mm/slub.c:3033
__slab_alloc+0x49/0x90 mm/slub.c:3120
slab_alloc_node mm/slub.c:3211 [inline]
slab_alloc mm/slub.c:3255 [inline]
__kmalloc_track_caller+0x169/0x2c0 mm/slub.c:4954
kmalloc_reserve net/core/skbuff.c:357 [inline]
__alloc_skb+0x210/0x730 net/core/skbuff.c:428
alloc_skb include/linux/skbuff.h:1183 [inline]
alloc_skb_with_frags+0xa8/0x620 net/core/skbuff.c:6207
sock_alloc_send_pskb+0x87f/0x9a0 net/core/sock.c:2542
unix_dgram_sendmsg+0x6f3/0x19b0 net/unix/af_unix.c:1816
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
sock_write_iter+0x2a6/0x3a0 net/socket.c:1079
call_write_iter include/linux/fs.h:2212 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x831/0xfd0 fs/read_write.c:594
ksys_write+0x14a/0x260 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
page_owner free stack trace missing

Memory state around the buggy address:
ffff8881103a1080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8881103a1100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8881103a1180: fb fb fb fb fb fb fb fb fb fb fb fb f


---
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 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.

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