Hello,
syzbot found the following issue on:
HEAD commit: 75cefdf153f5 Linux 6.1.127
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=177799f8580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=3dc848f1f9c50685
dashboard link:
https://syzkaller.appspot.com/bug?extid=084e2161dceb49dcef79
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/9fa70d9fd10a/disk-75cefdf1.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/d01cb9bb9789/vmlinux-75cefdf1.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/487423b91d50/bzImage-75cefdf1.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+084e21...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4539 at net/wireless/scan.c:1083 cfg80211_scan_done+0x376/0x580
Modules linked in:
CPU: 1 PID: 4539 Comm: kworker/u4:11 Not tainted 6.1.127-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:cfg80211_scan_done+0x376/0x580 net/wireless/scan.c:1082
Code: 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 02 9f 79 f7 0f 0b e9 a8 fd ff ff e8 f6 9e 79 f7 0f 0b e9 fc fd ff ff e8 ea 9e 79 f7 <0f> 0b e9 89 fe ff ff 48 c7 c1 38 29 9b 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90005377900 EFLAGS: 00010293
RAX: ffffffff8a10fdb6 RBX: ffff8880446301b8 RCX: ffff888030205940
RDX: 0000000000000000 RSI: ffffffff8b5e67a0 RDI: ffffffff8b5e6760
RBP: ffffc900053779d8 R08: ffffffff8a10fb8f R09: fffffbfff1d364e6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807b966000
R13: dffffc0000000000 R14: 1ffff1100f72cc0d R15: ffff88807b966068
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000300 CR3: 0000000031df8000 CR4: 00000000003506e0
DR0: 0000000000000008 DR1: 00000000000000ff DR2: fffffffffffffffb
DR3: 3e00000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ieee80211_scan_completed+0x507/0xa70 net/mac80211/scan.c:483
ieee80211_scan_work+0x16b/0x1d70 net/mac80211/scan.c:1169
cfg80211_wiphy_work+0x21a/0x250 net/wireless/core.c:433
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
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