Hello,
syzbot found the following issue on:
HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11e743fc980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link:
https://syzkaller.appspot.com/bug?extid=27fa463168bc04c57661
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/8b45ba80e02a/disk-88690811.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+27fa46...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in cfg80211_wext_freq+0x1f1/0x230 net/wireless/wext-compat.c:235
Read of size 2 at addr ffff888054b7ad40 by task syz-executor.2/4829
CPU: 0 PID: 4829 Comm: syz-executor.2 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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 mm/kasan/report.c:284 [inline]
print_report+0x15f/0x4f0 mm/kasan/report.c:395
kasan_report+0x136/0x160 mm/kasan/report.c:495
cfg80211_wext_freq+0x1f1/0x230 net/wireless/wext-compat.c:235
cfg80211_wext_siwscan+0x4ee/0x10c0 net/wireless/scan.c:2751
ioctl_standard_iw_point+0x780/0xca0 net/wireless/wext-core.c:848
ioctl_standard_call+0xc3/0x280 net/wireless/wext-core.c:1033
wext_ioctl_dispatch+0x16f/0x460 net/wireless/wext-core.c:997
wext_handle_ioctl+0x15b/0x260 net/wireless/wext-core.c:1058
sock_ioctl+0x13b/0x770 net/socket.c:1255
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa4e607cf69
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:00007fa4e6d500c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fa4e61b3f80 RCX: 00007fa4e607cf69
RDX: 0000000020000000 RSI: 0000000000008b18 RDI: 0000000000000003
RBP: 00007fa4e60da6fe R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fa4e61b3f80 R15: 00007ffe354d7368
</TASK>
Allocated by task 4829:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
____kasan_kmalloc mm/kasan/common.c:374 [inline]
__kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:383
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:955 [inline]
__kmalloc+0xb2/0x230 mm/slab_common.c:968
kmalloc include/linux/slab.h:561 [inline]
kzalloc include/linux/slab.h:692 [inline]
ioctl_standard_iw_point+0x4aa/0xca0 net/wireless/wext-core.c:809
ioctl_standard_call+0xc3/0x280 net/wireless/wext-core.c:1033
wext_ioctl_dispatch+0x16f/0x460 net/wireless/wext-core.c:997
wext_handle_ioctl+0x15b/0x260 net/wireless/wext-core.c:1058
sock_ioctl+0x13b/0x770 net/socket.c:1255
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
The buggy address belongs to the object at ffff888054b7ac00
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 320 bytes inside of
512-byte region [ffff888054b7ac00, ffff888054b7ae00)
The buggy address belongs to the physical page:
page:ffffea000152de00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x54b78
head:ffffea000152de00 order:2 compound_mapcount:0 compound_pincount:0
flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000010200 0000000000000000 dead000000000001 ffff888012441c80
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 0xd2a20(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 3625, tgid 3625 (kworker/1:6), ts 75888358523, free_ts
18578664979
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x18d/0x1b0 mm/page_alloc.c:2513
prep_new_page mm/page_alloc.c:2520 [inline]
get_page_from_freelist+0x31a1/0x3320 mm/page_alloc.c:4279
__alloc_pages+0x28d/0x770 mm/page_alloc.c:5547
alloc_slab_page+0x6a/0x150 mm/slub.c:1794
allocate_slab mm/slub.c:1939 [inline]
new_slab+0x84/0x2d0 mm/slub.c:1992
___slab_alloc+0xc20/0x1270 mm/slub.c:3180
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
__kmem_cache_alloc_node+0x19f/0x260 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:954 [inline]
__kmalloc_node_track_caller+0xa0/0x220 mm/slab_common.c:975
kmalloc_reserve net/core/skbuff.c:446 [inline]
__alloc_skb+0x135/0x670 net/core/skbuff.c:515
alloc_skb include/linux/skbuff.h:1271 [inline]
ndisc_alloc_skb+0xee/0x2c0 net/ipv6/ndisc.c:422
ndisc_send_rs+0x269/0x6a0 net/ipv6/ndisc.c:703
addrconf_dad_completed+0x788/0xcb0 net/ipv6/addrconf.c:4279
addrconf_dad_work+0xd8e/0x16b0
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1440 [inline]
free_pcp_prepare mm/page_alloc.c:1490 [inline]
free_unref_page_prepare+0xf63/0x1120 mm/page_alloc.c:3358
free_unref_page+0x33/0x3e0 mm/page_alloc.c:3453
free_contig_range+0x9a/0x150 mm/page_alloc.c:9507
destroy_args+0xfe/0x997 mm/debug_vm_pgtable.c:1031
debug_vm_pgtable+0x416/0x46b mm/debug_vm_pgtable.c:1354
do_one_initcall+0x265/0x8f0 init/main.c:1299
do_initcall_level+0x157/0x207 init/main.c:1372
do_initcalls+0x49/0x86 init/main.c:1388
kernel_init_freeable+0x45c/0x60f init/main.c:1627
kernel_init+0x19/0x290 init/main.c:1515
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
Memory state around the buggy address:
ffff888054b7ac00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888054b7ac80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888054b7ad00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff888054b7ad80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888054b7ae00: 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