[syzbot] [wireless?] KASAN: slab-out-of-bounds Read in ieee80211_ie_split_ric (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5d41f95f5d0b dpll: zl3073x: Fix output pin phase adjustmen..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=16b43d3a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3161cabe5a361ff
dashboard link: https://syzkaller.appspot.com/bug?extid=1d7461ceeccc7e92d309
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/182b4bb52a10/disk-5d41f95f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4a86438e761e/vmlinux-5d41f95f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/29465cf28ab1/bzImage-5d41f95f.xz

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

==================================================================
BUG: KASAN: slab-out-of-bounds in skip_ie net/wireless/util.c:1967 [inline]
BUG: KASAN: slab-out-of-bounds in ieee80211_ie_split_ric+0x8fa/0x950 net/wireless/util.c:-1
Read of size 1 at addr ffff88802946afa1 by task syz.3.11380/15499

CPU: 0 UID: 0 PID: 15499 Comm: syz.3.11380 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0xba/0x230 mm/kasan/report.c:482
kasan_report+0x117/0x150 mm/kasan/report.c:595
skip_ie net/wireless/util.c:1967 [inline]
ieee80211_ie_split_ric+0x8fa/0x950 net/wireless/util.c:-1
ieee80211_ie_split include/net/cfg80211.h:9693 [inline]
cfg80211_sme_get_conn_ies net/wireless/sme.c:529 [inline]
cfg80211_sme_connect net/wireless/sme.c:586 [inline]
cfg80211_connect+0x11f8/0x2140 net/wireless/sme.c:1527
cfg80211_mgd_wext_connect+0x4a0/0x5f0 net/wireless/wext-sme.c:57
cfg80211_wext_siwessid+0xc4/0x160 net/wireless/wext-compat.c:1412
ioctl_standard_iw_point+0x6cd/0xd90 net/wireless/wext-core.c:865
ioctl_standard_call+0xaf/0x1b0 net/wireless/wext-core.c:1050
wireless_process_ioctl net/wireless/wext-core.c:-1 [inline]
wext_ioctl_dispatch+0xee/0x410 net/wireless/wext-core.c:1014
wext_handle_ioctl+0x10f/0x1d0 net/wireless/wext-core.c:1075
sock_ioctl+0x159/0x7f0 net/socket.c:1307
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa2c219aeb9
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:00007fa2c307b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fa2c2415fa0 RCX: 00007fa2c219aeb9
RDX: 0000200000000040 RSI: 0000000000008b1a RDI: 0000000000000005
RBP: 00007fa2c2208c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa2c2416038 R14: 00007fa2c2415fa0 R15: 00007ffd00308408
</TASK>

Allocated by task 5139:
kasan_save_stack mm/kasan/common.c:57 [inline]
kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
poison_kmalloc_redzone mm/kasan/common.c:398 [inline]
__kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:415
kasan_kmalloc include/linux/kasan.h:263 [inline]
__do_kmalloc_node mm/slub.c:5657 [inline]
__kmalloc_node_track_caller_noprof+0x558/0x7f0 mm/slub.c:5768
kmemdup_noprof+0x2b/0x70 mm/util.c:138
kmemdup_noprof include/linux/fortify-string.h:765 [inline]
cfg80211_wext_siwgenie+0x1ad/0x320 net/wireless/wext-sme.c:322
ioctl_standard_iw_point+0x6cd/0xd90 net/wireless/wext-core.c:865
ioctl_standard_call+0xaf/0x1b0 net/wireless/wext-core.c:1050
wireless_process_ioctl net/wireless/wext-core.c:-1 [inline]
wext_ioctl_dispatch+0xee/0x410 net/wireless/wext-core.c:1014
wext_handle_ioctl+0x10f/0x1d0 net/wireless/wext-core.c:1075
sock_ioctl+0x159/0x7f0 net/socket.c:1307
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff88802946afa0
which belongs to the cache kmalloc-8 of size 8
The buggy address is located 0 bytes to the right of
allocated 1-byte region [ffff88802946afa0, ffff88802946afa1)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff88802946a1c0 pfn:0x2946a
flags: 0xfff00000000200(workingset|node=0|zone=1|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 00fff00000000200 ffff88813fe26500 ffffea00015f0210 ffffea0002018250
raw: ffff88802946a1c0 0000000000800079 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x52cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP), pid 4276, tgid 4272 (syz.2.8413), ts 893909570156, free_ts 893627728021
set_page_owner include/linux/page_owner.h:32 [inline]
post_alloc_hook+0x228/0x280 mm/page_alloc.c:1884
prep_new_page mm/page_alloc.c:1892 [inline]
get_page_from_freelist+0x24dc/0x2580 mm/page_alloc.c:3945
__alloc_frozen_pages_noprof+0x18d/0x380 mm/page_alloc.c:5240
alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2486
alloc_slab_page mm/slub.c:3075 [inline]
allocate_slab+0x86/0x3a0 mm/slub.c:3248
new_slab mm/slub.c:3302 [inline]
___slab_alloc+0xd82/0x1760 mm/slub.c:4656
__slab_alloc+0x65/0x100 mm/slub.c:4779
__slab_alloc_node mm/slub.c:4855 [inline]
slab_alloc_node mm/slub.c:5251 [inline]
__do_kmalloc_node mm/slub.c:5656 [inline]
__kmalloc_node_track_caller_noprof+0x5b7/0x7f0 mm/slub.c:5768
__kmemdup_nul mm/util.c:64 [inline]
kstrdup+0x42/0x100 mm/util.c:84
__kernfs_new_node+0xa9/0x8e0 fs/kernfs/dir.c:633
kernfs_new_node+0x102/0x210 fs/kernfs/dir.c:718
__kernfs_create_file+0x4b/0x2e0 fs/kernfs/file.c:1057
sysfs_add_file_mode_ns+0x238/0x300 fs/sysfs/file.c:313
create_files fs/sysfs/group.c:82 [inline]
internal_create_group+0x673/0x1180 fs/sysfs/group.c:189
internal_create_groups fs/sysfs/group.c:229 [inline]
sysfs_create_groups+0x59/0x120 fs/sysfs/group.c:255
setup_port drivers/infiniband/core/sysfs.c:1247 [inline]
ib_setup_port_attrs+0xe1b/0x2140 drivers/infiniband/core/sysfs.c:1433
page last free pid 23 tgid 23 stack trace:
reset_page_owner include/linux/page_owner.h:25 [inline]
free_pages_prepare mm/page_alloc.c:1433 [inline]
__free_frozen_pages+0xbf8/0xd70 mm/page_alloc.c:2973
__tlb_remove_table_free mm/mmu_gather.c:228 [inline]
tlb_remove_table_rcu+0x85/0x100 mm/mmu_gather.c:291
rcu_do_batch kernel/rcu/tree.c:2605 [inline]
rcu_core+0xc9e/0x1750 kernel/rcu/tree.c:2857
handle_softirqs+0x22a/0x7c0 kernel/softirq.c:622
run_ksoftirqd+0x36/0x60 kernel/softirq.c:1063
smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160
kthread+0x726/0x8b0 kernel/kthread.c:463
ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246

Memory state around the buggy address:
ffff88802946ae80: fa fc fc fc 04 fc fc fc 04 fc fc fc fa fc fc fc
ffff88802946af00: 04 fc fc fc 04 fc fc fc 04 fc fc fc 04 fc fc fc
>ffff88802946af80: 04 fc fc fc 01 fc fc fc 04 fc fc fc 04 fc fc fc
^
ffff88802946b000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff88802946b080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


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