| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <688119a0.050a0220.248954.0007.GAE@google.com> Date: Wed, 23 Jul 2025 10:19:28 -0700 From: syzbot <syzbot+d6ccd49ae046542a0641@...kaller.appspotmail.com> To: dakr@...nel.org, gregkh@...uxfoundation.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, rafael@...nel.org, syzkaller-bugs@...glegroups.com Subject: [syzbot] [fs?] [wireless?] general protection fault in simple_recursive_removal (5) Hello, syzbot found the following issue on: HEAD commit: 89be9a83ccf1 Linux 6.16-rc7 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11b42fd4580000 kernel config: https://syzkaller.appspot.com/x/.config?x=8adfe52da0de2761 dashboard link: https://syzkaller.appspot.com/bug?extid=d6ccd49ae046542a0641 compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=134baf22580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d5a4f0580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-89be9a83.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a3f5f507f252/vmlinux-89be9a83.xz kernel image: https://storage.googleapis.com/syzbot-assets/a8f9b92c57a6/bzImage-89be9a83.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d6ccd49ae046542a0641@...kaller.appspotmail.com wlan1: send auth to aa:09:b7:99:c0:d7 (try 2/3) wlan1: send auth to aa:09:b7:99:c0:d7 (try 3/3) wlan1: authentication with aa:09:b7:99:c0:d7 timed out Oops: general protection fault, probably for non-canonical address 0xdffffc0000000029: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000148-0x000000000000014f] CPU: 0 UID: 0 PID: 171 Comm: kworker/u4:4 Not tainted 6.16.0-rc7-syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Workqueue: events_unbound cfg80211_wiphy_work RIP: 0010:kasan_byte_accessible+0x12/0x30 mm/kasan/generic.c:199 Code: 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cc cc cc cc 66 66 66 66 66 66 2e RSP: 0018:ffffc90001977400 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff8b713286 RCX: ca5c1933e35f3700 RDX: 0000000000000000 RSI: ffffffff8b713286 RDI: 0000000000000029 RBP: ffffffff824067f0 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffed10085cf24c R12: 0000000000000000 R13: 0000000000000148 R14: 0000000000000148 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff88808d218000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2f55ffff CR3: 000000005030a000 CR4: 0000000000352ef0 Call Trace: <TASK> __kasan_check_byte+0x12/0x40 mm/kasan/common.c:556 kasan_check_byte include/linux/kasan.h:399 [inline] lock_acquire+0x8d/0x360 kernel/locking/lockdep.c:5845 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:869 [inline] simple_recursive_removal+0x90/0x690 fs/libfs.c:616 debugfs_remove+0x5b/0x70 fs/debugfs/inode.c:805 ieee80211_sta_debugfs_remove+0x40/0x70 net/mac80211/debugfs_sta.c:1279 __sta_info_destroy_part2+0x352/0x450 net/mac80211/sta_info.c:1501 __sta_info_destroy net/mac80211/sta_info.c:1517 [inline] sta_info_destroy_addr+0xf5/0x140 net/mac80211/sta_info.c:1529 ieee80211_destroy_auth_data+0x12d/0x260 net/mac80211/mlme.c:4597 ieee80211_sta_work+0x11cf/0x3600 net/mac80211/mlme.c:8310 cfg80211_wiphy_work+0x2df/0x460 net/wireless/core.c:435 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:kasan_byte_accessible+0x12/0x30 mm/kasan/generic.c:199 Code: 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df <0f> b6 04 07 3c 08 0f 92 c0 c3 cc cc cc cc cc 66 66 66 66 66 66 2e RSP: 0018:ffffc90001977400 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: ffffffff8b713286 RCX: ca5c1933e35f3700 RDX: 0000000000000000 RSI: ffffffff8b713286 RDI: 0000000000000029 RBP: ffffffff824067f0 R08: 0000000000000001 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffed10085cf24c R12: 0000000000000000 R13: 0000000000000148 R14: 0000000000000148 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff88808d218000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2f55ffff CR3: 0000000011601000 CR4: 0000000000352ef0 ---------------- Code disassembly (best guess): 0: 0f 1f 84 00 00 00 00 nopl 0x0(%rax,%rax,1) 7: 00 8: 90 nop 9: 90 nop a: 90 nop b: 90 nop c: 90 nop d: 90 nop e: 90 nop f: 90 nop 10: 90 nop 11: 90 nop 12: 90 nop 13: 90 nop 14: 90 nop 15: 90 nop 16: 90 nop 17: 90 nop 18: 66 0f 1f 00 nopw (%rax) 1c: 48 c1 ef 03 shr $0x3,%rdi 20: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax 27: fc ff df * 2a: 0f b6 04 07 movzbl (%rdi,%rax,1),%eax <-- trapping instruction 2e: 3c 08 cmp $0x8,%al 30: 0f 92 c0 setb %al 33: c3 ret 34: cc int3 35: cc int3 36: cc int3 37: cc int3 38: cc int3 39: 66 data16 3a: 66 data16 3b: 66 data16 3c: 66 data16 3d: 66 data16 3e: 66 data16 3f: 2e cs --- 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 syzkaller@...glegroups.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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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
Powered by blists - more mailing lists