From: syzbot <syzbot+cc867e537e4bd36f69bb@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] KASAN: slab-out-of-bounds Read in ieee80211_ie_split_ric (3)
Date: Fri, 24 Jul 2026 19:44:03 -0700 [thread overview]
Message-ID: <6a6422f3.073198cf.94f0f.000e.GAE@google.com> (raw)
In-Reply-To: <20260725015331.19649-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: slab-out-of-bounds Read in ieee80211_ie_split_ric
==================================================================
BUG: KASAN: slab-out-of-bounds in skip_ie net/wireless/util.c:2068 [inline]
BUG: KASAN: slab-out-of-bounds in ieee80211_ie_split_ric+0x5a7/0x610 net/wireless/util.c:2124
Read of size 1 at addr ffff88802db83901 by task syz.0.18/6258
CPU: 2 UID: 0 PID: 6258 Comm: syz.0.18 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0x13d/0x4b0 mm/kasan/report.c:482
kasan_report+0xdf/0x1c0 mm/kasan/report.c:595
skip_ie net/wireless/util.c:2068 [inline]
ieee80211_ie_split_ric+0x5a7/0x610 net/wireless/util.c:2124
ieee80211_ie_split include/net/cfg80211.h:10226 [inline]
cfg80211_sme_get_conn_ies net/wireless/sme.c:529 [inline]
cfg80211_sme_connect net/wireless/sme.c:586 [inline]
cfg80211_connect+0x18a9/0x1ff0 net/wireless/sme.c:1528
cfg80211_mgd_wext_connect+0x57d/0x6d0 net/wireless/wext-sme.c:57
cfg80211_mgd_wext_siwessid+0x36e/0x750 net/wireless/wext-sme.c:184
cfg80211_wext_siwessid+0xd2/0x140 net/wireless/wext-compat.c:1415
ioctl_standard_iw_point+0x5b4/0xc90 net/wireless/wext-core.c:864
ioctl_standard_call+0x167/0x1d0 net/wireless/wext-core.c:1049
wireless_process_ioctl net/wireless/wext-core.c:980 [inline]
wext_ioctl_dispatch.constprop.0+0x312/0x3e0 net/wireless/wext-core.c:1013
wext_handle_ioctl+0x105/0x1b0 net/wireless/wext-core.c:1074
sock_ioctl+0x2d4/0x6b0 net/socket.c:1353
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f52bb39de59
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:00007f52bc1bc028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f52bb625fa0 RCX: 00007f52bb39de59
RDX: 0000200000000040 RSI: 0000000000008b1a RDI: 0000000000000006
RBP: 00007f52bb433e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f52bb626038 R14: 00007f52bb625fa0 R15: 00007ffd21f807e8
</TASK>
Allocated by task 6258:
kasan_save_stack+0x30/0x50 mm/kasan/common.c:57
kasan_save_track+0x14/0x30 mm/kasan/common.c:78
poison_kmalloc_redzone mm/kasan/common.c:398 [inline]
__kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:415
kasan_kmalloc include/linux/kasan.h:263 [inline]
__do_kmalloc_node mm/slub.c:5362 [inline]
__kmalloc_node_track_caller_noprof+0x331/0x830 mm/slub.c:5497
kmemdup_noprof+0x29/0x60 mm/util.c:138
kmemdup_noprof include/linux/fortify-string.h:715 [inline]
cfg80211_wext_siwgenie+0x375/0x500 net/wireless/wext-sme.c:330
ioctl_standard_iw_point+0x5b4/0xc90 net/wireless/wext-core.c:864
ioctl_standard_call+0x167/0x1d0 net/wireless/wext-core.c:1049
wireless_process_ioctl net/wireless/wext-core.c:980 [inline]
wext_ioctl_dispatch.constprop.0+0x312/0x3e0 net/wireless/wext-core.c:1013
wext_handle_ioctl+0x105/0x1b0 net/wireless/wext-core.c:1074
sock_ioctl+0x2d4/0x6b0 net/socket.c:1353
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
The buggy address belongs to the object at ffff88802db83900
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 [ffff88802db83900, ffff88802db83901)
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff88802db83b20 pfn:0x2db83
flags: 0xfff00000000200(workingset|node=0|zone=1|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 00fff00000000200 ffff88801bc42500 ffffea0000a9f590 ffffea0000b15710
raw: ffff88802db83b20 0000000800800074 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 0xd2c00(GFP_NOIO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, tgid 1 (swapper/0), ts 11550758066, free_ts 0
set_page_owner include/linux/page_owner.h:32 [inline]
post_alloc_hook+0xfd/0x120 mm/page_alloc.c:1859
prep_new_page mm/page_alloc.c:1867 [inline]
get_page_from_freelist+0xf48/0x3530 mm/page_alloc.c:3946
__alloc_frozen_pages_noprof+0x299/0x2dc0 mm/page_alloc.c:5304
alloc_slab_page mm/slub.c:3294 [inline]
allocate_slab mm/slub.c:3408 [inline]
new_slab+0xa2/0x650 mm/slub.c:3454
refill_objects+0xe3/0x410 mm/slub.c:7338
refill_sheaf mm/slub.c:2832 [inline]
__pcs_replace_empty_main+0x376/0x680 mm/slub.c:4703
alloc_from_pcs mm/slub.c:4801 [inline]
slab_alloc_node mm/slub.c:4933 [inline]
__kmalloc_cache_noprof+0x479/0x6c0 mm/slub.c:5511
_kmalloc_noprof include/linux/slab.h:969 [inline]
usb_control_msg+0xbc/0x4b0 drivers/usb/core/message.c:157
set_port_feature drivers/usb/core/hub.c:466 [inline]
hub_power_on+0x193/0x4f0 drivers/usb/core/hub.c:979
hub_activate+0x146e/0x1c40 drivers/usb/core/hub.c:1139
hub_configure drivers/usb/core/hub.c:1766 [inline]
hub_probe.cold+0x2eca/0x2eda drivers/usb/core/hub.c:2001
usb_probe_interface+0x303/0x8f0 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:628 [inline]
really_probe+0x241/0xa60 drivers/base/dd.c:706
__driver_probe_device+0x20e/0x450 drivers/base/dd.c:868
driver_probe_device+0x4a/0x140 drivers/base/dd.c:898
__device_attach_driver+0x1df/0x320 drivers/base/dd.c:1026
page_owner free stack trace missing
Memory state around the buggy address:
ffff88802db83800: fa fc fc fc 06 fc fc fc 07 fc fc fc 00 fc fc fc
ffff88802db83880: 06 fc fc fc 06 fc fc fc fa fc fc fc 05 fc fc fc
>ffff88802db83900: 01 fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc
^
ffff88802db83980: fa fc fc fc fa fc fc fc 06 fc fc fc 06 fc fc fc
ffff88802db83a00: 00 fc fc fc 00 fc fc fc 00 fc fc fc 00 fc fc fc
==================================================================
Tested on:
commit: b66b0005 Merge branches 'for-next/fixes' and 'for-next..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=11baa6b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d69870d5e052935f
dashboard link: https://syzkaller.appspot.com/bug?extid=cc867e537e4bd36f69bb
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=16aaa6b9580000
next parent reply other threads:[~2026-07-25 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260725015331.19649-1-kartikey406@gmail.com>
2026-07-25 2:44 ` syzbot [this message]
[not found] <20260725040920.24092-1-kartikey406@gmail.com>
2026-07-25 4:37 ` [syzbot] [wireless?] KASAN: slab-out-of-bounds Read in ieee80211_ie_split_ric (3) syzbot
[not found] <20260710013714.15699-1-kartikey406@gmail.com>
2026-07-10 2:33 ` syzbot
2026-07-09 16:33 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a6422f3.073198cf.94f0f.000e.GAE@google.com \
--to=syzbot+cc867e537e4bd36f69bb@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.