Hello,
syzbot found the following issue on:
HEAD commit: bf32db543281 ANDROID: GKI: update xiaomi symbol list
git tree: android14-6.1
console output:
https://syzkaller.appspot.com/x/log.txt?x=15fe33d2580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=69841d35933a4e41
dashboard link:
https://syzkaller.appspot.com/bug?extid=7b261708d878bd949ebc
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=113748ae580000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=13fe33d2580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b0af0e459d63/disk-bf32db54.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/99d96ebb58b6/vmlinux-bf32db54.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/cb45eb366201/bzImage-bf32db54.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7b2617...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: use-after-free in instrument_atomic_read_write include/linux/instrumented.h:102 [inline]
BUG: KASAN: use-after-free in atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:1779 [inline]
BUG: KASAN: use-after-free in __mutex_trylock_fast kernel/locking/mutex.c:176 [inline]
BUG: KASAN: use-after-free in mutex_lock+0x86/0x1b0 kernel/locking/mutex.c:295
Write of size 8 at addr ffff888111ff6150 by task syz.2.17/375
CPU: 0 PID: 375 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
__dump_stack+0x21/0x24 lib/dump_stack.c:88
dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
print_address_description+0x71/0x200 mm/kasan/report.c:316
print_report+0x4a/0x60 mm/kasan/report.c:420
kasan_report+0x122/0x150 mm/kasan/report.c:524
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x249/0x2a0 mm/kasan/generic.c:189
__kasan_check_write+0x14/0x20 mm/kasan/shadow.c:37
instrument_atomic_read_write include/linux/instrumented.h:102 [inline]
atomic_long_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:1779 [inline]
__mutex_trylock_fast kernel/locking/mutex.c:176 [inline]
mutex_lock+0x86/0x1b0 kernel/locking/mutex.c:295
pppol2tp_release+0x194/0x2d0 net/l2tp/l2tp_ppp.c:441
__sock_release net/socket.c:652 [inline]
sock_close+0xf1/0x290 net/socket.c:1389
__fput+0x1fc/0x8f0 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x1e1/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0x9b/0xb0 kernel/entry/common.c:177
exit_to_user_mode_prepare+0x87/0xd0 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8b2d79ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffea137b878 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007ffea137b960 RCX: 00007f8b2d79ce59
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 000000000000699c R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b33120000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8b2da15fac R14: 00007f8b2da15fa8 R15: 00007f8b2da15fa0
</TASK>
Allocated by task 375:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_alloc_info+0x25/0x30 mm/kasan/generic.c:505
____kasan_kmalloc mm/kasan/common.c:380 [inline]
__kasan_kmalloc+0x95/0xb0 mm/kasan/common.c:389
kasan_kmalloc include/linux/kasan.h:212 [inline]
__do_kmalloc_node mm/slab_common.c:938 [inline]
__kmalloc+0xb1/0x1e0 mm/slab_common.c:951
kmalloc include/linux/slab.h:568 [inline]
kzalloc include/linux/slab.h:699 [inline]
l2tp_session_create+0x38/0xbe0 net/l2tp/l2tp_core.c:1609
pppol2tp_connect+0xbef/0x1620 net/l2tp/l2tp_ppp.c:771
__sys_connect_file net/socket.c:2000 [inline]
__sys_connect+0x3da/0x460 net/socket.c:2017
__do_sys_connect net/socket.c:2027 [inline]
__se_sys_connect net/socket.c:2024 [inline]
__x64_sys_connect+0x7a/0x90 net/socket.c:2024
x64_sys_call+0x88d/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:43
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Freed by task 375:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_free_info+0x31/0x50 mm/kasan/generic.c:516
____kasan_slab_free+0x132/0x180 mm/kasan/common.c:242
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:250
kasan_slab_free include/linux/kasan.h:178 [inline]
slab_free_hook mm/slub.c:1750 [inline]
slab_free_freelist_hook+0xc2/0x190 mm/slub.c:1776
slab_free mm/slub.c:3712 [inline]
__kmem_cache_free+0xb7/0x1b0 mm/slub.c:3728
kfree+0x6f/0xf0 mm/slab_common.c:990
l2tp_session_free net/l2tp/l2tp_core.c:168 [inline]
l2tp_session_put+0xaf/0x1a0 net/l2tp/l2tp_core.c:193
l2tp_session_delete+0x3f0/0x4e0 net/l2tp/l2tp_core.c:1582
pppol2tp_release+0x185/0x2d0 net/l2tp/l2tp_ppp.c:438
__sock_release net/socket.c:652 [inline]
sock_close+0xf1/0x290 net/socket.c:1389
__fput+0x1fc/0x8f0 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x1e1/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0x9b/0xb0 kernel/entry/common.c:177
exit_to_user_mode_prepare+0x87/0xd0 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
The buggy address belongs to the object at ffff888111ff6000
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 336 bytes inside of
512-byte region [ffff888111ff6000, ffff888111ff6200)
The buggy address belongs to the physical page:
page:ffffea000447fd00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x111ff4
head:ffffea000447fd00 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x4000000000010200(slab|head|zone=1)
raw: 4000000000010200 0000000000000000 dead000000000122 ffff888100042f00
raw: 0000000000000000 0000000080100010 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 0x1d20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL), pid 370, tgid 370 (syz-executor), ts 27058489462, free_ts 25972300204
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1f5/0x210 mm/page_alloc.c:2672
prep_new_page+0x1c/0x110 mm/page_alloc.c:2679
get_page_from_freelist+0x2d12/0x2d80 mm/page_alloc.c:4585
__alloc_pages+0x1fa/0x610 mm/page_alloc.c:5929
alloc_slab_page+0x6e/0xf0 include/linux/gfp.h:-1
allocate_slab mm/slub.c:1967 [inline]
new_slab+0x98/0x3d0 mm/slub.c:2020
___slab_alloc+0x6bd/0xb20 mm/slub.c:3177
__slab_alloc+0x5e/0xa0 mm/slub.c:3263
slab_alloc_node mm/slub.c:3348 [inline]
__kmem_cache_alloc_node+0x203/0x2c0 mm/slub.c:3423
kmalloc_trace+0x29/0xb0 mm/slab_common.c:1028
kmalloc include/linux/slab.h:563 [inline]
kzalloc include/linux/slab.h:699 [inline]
blkcg_css_alloc+0x65/0xc40 block/blk-cgroup.c:1176
css_create kernel/cgroup/cgroup.c:5623 [inline]
cgroup_apply_control_enable+0x392/0xe10 kernel/cgroup/cgroup.c:3315
cgroup_mkdir+0x1167/0x13c0 kernel/cgroup/cgroup.c:5842
kernfs_iop_mkdir+0x1bb/0x2c0 fs/kernfs/dir.c:1221
vfs_mkdir+0x39c/0x580 fs/namei.c:4113
do_mkdirat+0x171/0x4c0 fs/namei.c:4138
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1580 [inline]
free_pcp_prepare mm/page_alloc.c:1654 [inline]
free_unref_page_prepare+0x7f8/0x800 mm/page_alloc.c:3620
free_unref_page+0x95/0x540 mm/page_alloc.c:3718
free_the_page mm/page_alloc.c:863 [inline]
__free_pages+0x67/0x100 mm/page_alloc.c:6019
__free_slab+0xca/0x1a0 mm/slub.c:2044
free_slab mm/slub.c:2059 [inline]
discard_slab mm/slub.c:2065 [inline]
__unfreeze_partials+0x160/0x190 mm/slub.c:2614
put_cpu_partial+0xa9/0x100 mm/slub.c:2690
__slab_free+0x1c4/0x280 mm/slub.c:3589
do_slab_free mm/slub.c:3666 [inline]
___cache_free+0xbf/0xd0 mm/slub.c:3722
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0xc6/0x140 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x14a/0x170 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x24/0x80 mm/kasan/common.c:311
kasan_slab_alloc include/linux/kasan.h:202 [inline]
slab_post_alloc_hook+0x4f/0x2d0 mm/slab.h:768
slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc mm/slub.c:3392 [inline]
__kmem_cache_alloc_lru mm/slub.c:3399 [inline]
kmem_cache_alloc+0x16e/0x330 mm/slub.c:3408
getname_flags+0xb9/0x500 fs/namei.c:139
user_path_at_empty+0x30/0x1c0 fs/namei.c:2911
do_readlinkat+0xd9/0x490 fs/stat.c:468
Memory state around the buggy address:
ffff888111ff6000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888111ff6080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888111ff6100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888111ff6180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888111ff6200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
---
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