[v5.15] KASAN: use-after-free Read in ax25_find_cb

2 views
Skip to first unread message

syzbot

unread,
Jul 22, 2025, 8:35:36 PM7/22/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13bc2fd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=c18cee25361d947bc14b
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

==================================================================
BUG: KASAN: use-after-free in ax25_find_cb+0x174/0x3a0 net/ax25/af_ax25.c:232
Read of size 8 at addr ffff0000d2e8b408 by task syz.3.742/6655

CPU: 0 PID: 6655 Comm: syz.3.742 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call trace:
dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
print_address_description+0x78/0x30c mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xec/0x15c mm/kasan/report.c:451
__asan_report_load8_noabort+0x44/0x50 mm/kasan/report_generic.c:309
ax25_find_cb+0x174/0x3a0 net/ax25/af_ax25.c:232
rose_link_up net/rose/rose_link.c:129 [inline]
rose_transmit_link+0x168/0x680 net/rose/rose_link.c:271
rose_write_internal+0xee8/0x17c4 net/rose/rose_subr.c:198
rose_connect+0x8f0/0xffc net/rose/af_rose.c:875
__sys_connect_file net/socket.c:1923 [inline]
__sys_connect+0x264/0x28c net/socket.c:1940
__do_sys_connect net/socket.c:1950 [inline]
__se_sys_connect net/socket.c:1947 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:1947
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Allocated by task 5896:
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 mm/kasan/common.c:513 [inline]
__kasan_kmalloc+0xb0/0xf0 mm/kasan/common.c:522
kasan_kmalloc include/linux/kasan.h:264 [inline]
kmem_cache_alloc_trace+0x274/0x3fc mm/slub.c:3247
kmalloc include/linux/slab.h:604 [inline]
kzalloc include/linux/slab.h:735 [inline]
ax25_dev_device_up+0x5c/0x540 net/ax25/ax25_dev.c:55
ax25_device_event+0x504/0x590 net/ax25/af_ax25.c:139
notifier_call_chain kernel/notifier.c:83 [inline]
raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
call_netdevice_notifiers net/core/dev.c:2075 [inline]
__dev_notify_flags+0x250/0x46c net/core/dev.c:-1
dev_change_flags+0xc8/0x154 net/core/dev.c:8929
dev_ifsioc+0x504/0xef4 net/core/dev_ioctl.c:324
dev_ioctl+0x4d0/0xc94 net/core/dev_ioctl.c:587
sock_do_ioctl+0x18c/0x240 net/socket.c:1154
sock_ioctl+0x5c8/0x87c net/socket.c:1257
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Freed by task 6628:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4c/0x84 mm/kasan/common.c:46
kasan_set_free_info+0x28/0x4c mm/kasan/generic.c:360
____kasan_slab_free+0x118/0x164 mm/kasan/common.c:366
__kasan_slab_free+0x18/0x28 mm/kasan/common.c:374
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0x128/0x1e8 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kfree+0x170/0x40c mm/slub.c:4559
ax25_dev_put include/net/ax25.h:302 [inline]
ax25_release+0x564/0x814 net/ax25/af_ax25.c:1062
__sock_release net/socket.c:649 [inline]
sock_close+0xb4/0x1f8 net/socket.c:1336
__fput+0x1c0/0x7f8 fs/file_table.c:311
____fput+0x20/0x30 fs/file_table.c:339
task_work_run+0x12c/0x1e0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
do_notify_resume+0x24b4/0x3128 arch/arm64/kernel/signal.c:949
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Last potentially related work creation:
kasan_save_stack+0x38/0x68 mm/kasan/common.c:38
kasan_record_aux_stack+0xcc/0x114 mm/kasan/generic.c:348
insert_work+0x64/0x388 kernel/workqueue.c:1366
__queue_work+0xb30/0x1054 kernel/workqueue.c:1532
queue_work_on+0xc4/0x17c kernel/workqueue.c:1559
queue_work include/linux/workqueue.h:512 [inline]
netdevice_queue_work drivers/infiniband/core/roce_gid_mgmt.c:659 [inline]
netdevice_event+0x6ac/0x79c drivers/infiniband/core/roce_gid_mgmt.c:802
notifier_call_chain kernel/notifier.c:83 [inline]
raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
call_netdevice_notifiers net/core/dev.c:2075 [inline]
dev_set_mac_address+0x264/0x38c net/core/dev.c:9114
dev_set_mac_address_user+0x44/0x68 net/core/dev.c:9128
do_setlink+0x6a0/0x3088 net/core/rtnetlink.c:2734
__rtnl_newlink net/core/rtnetlink.c:3450 [inline]
rtnl_newlink+0x10d0/0x1404 net/core/rtnetlink.c:3572
rtnetlink_rcv_msg+0x9d4/0xd04 net/core/rtnetlink.c:5650
netlink_rcv_skb+0x208/0x3c4 net/netlink/af_netlink.c:2507
rtnetlink_rcv+0x28/0x38 net/core/rtnetlink.c:5668
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x624/0x8b0 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6e8/0x9cc net/netlink/af_netlink.c:1918
sock_sendmsg_nosec net/socket.c:704 [inline]
__sock_sendmsg net/socket.c:716 [inline]
__sys_sendto+0x2e8/0x3d8 net/socket.c:2063
__do_sys_sendto net/socket.c:2075 [inline]
__se_sys_sendto net/socket.c:2071 [inline]
__arm64_sys_sendto+0xd8/0xf8 net/socket.c:2071
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Second to last potentially related work creation:
kasan_save_stack+0x38/0x68 mm/kasan/common.c:38
kasan_record_aux_stack+0xcc/0x114 mm/kasan/generic.c:348
insert_work+0x64/0x388 kernel/workqueue.c:1366
__queue_work+0xb30/0x1054 kernel/workqueue.c:1532
queue_work_on+0xc4/0x17c kernel/workqueue.c:1559
queue_work include/linux/workqueue.h:512 [inline]
call_usermodehelper_exec+0x22c/0x478 kernel/umh.c:435
kobject_uevent_env+0x670/0x888 lib/kobject_uevent.c:633
kobject_uevent+0x2c/0x3c lib/kobject_uevent.c:657
rx_queue_add_kobject net/core/net-sysfs.c:1070 [inline]
net_rx_queue_update_kobjects+0x1e0/0x420 net/core/net-sysfs.c:1110
register_queue_kobjects net/core/net-sysfs.c:1767 [inline]
netdev_register_kobject+0x1e4/0x2d4 net/core/net-sysfs.c:2018
register_netdevice+0xd44/0x1304 net/core/dev.c:10397
register_netdev+0x48/0x64 net/core/dev.c:10521
nr_proto_init+0x164/0x6f0 net/netrom/af_netrom.c:1424
do_one_initcall+0x228/0x8b0 init/main.c:1302
do_initcall_level+0x154/0x214 init/main.c:1375
do_initcalls+0x58/0xac init/main.c:1391
do_basic_setup+0x8c/0xa0 init/main.c:1410
kernel_init_freeable+0x404/0x5fc init/main.c:1615
kernel_init+0x24/0x1d0 init/main.c:1506
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:855

The buggy address belongs to the object at ffff0000d2e8b400
which belongs to the cache kmalloc-256 of size 256
The buggy address is located 8 bytes inside of
256-byte region [ffff0000d2e8b400, ffff0000d2e8b500)
The buggy address belongs to the page:
page:00000000a21fbad6 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112e8a
head:00000000a21fbad6 order:1 compound_mapcount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 fffffc00031fb680 0000000200000002 ffff0000c0002480
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000d2e8b300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000d2e8b380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000d2e8b400: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff0000d2e8b480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff0000d2e8b500: 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 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

syzbot

unread,
Nov 29, 2025, 9:07:13 PM11/29/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages