All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+de3ee5362db09487ea37@syzkaller.appspotmail.com>
To: johannes@sipsolutions.net, linux-kernel@vger.kernel.org,
	 linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] WARNING in ieee80211_free_keys (2)
Date: Sat, 09 Aug 2025 03:09:26 -0700	[thread overview]
Message-ID: <68971e56.a70a0220.7865.0031.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    d2eedaa3909b Merge tag 'rtc-6.17' of git://git.kernel.org/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=178886a2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=75e522434dc68cb9
dashboard link: https://syzkaller.appspot.com/bug?extid=de3ee5362db09487ea37
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/73ccac85e612/disk-d2eedaa3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/33b13def715b/vmlinux-d2eedaa3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/930b192c99ba/bzImage-d2eedaa3.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 12058 at net/mac80211/key.c:1163 ieee80211_free_keys+0x536/0x650 net/mac80211/key.c:1162
Modules linked in:
CPU: 0 UID: 0 PID: 12058 Comm: kworker/u8:17 Not tainted 6.16.0-syzkaller-11489-gd2eedaa3909b #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: netns cleanup_net
RIP: 0010:ieee80211_free_keys+0x536/0x650 net/mac80211/key.c:1162
Code: 00 00 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 f9 3c c7 f6 90 0f 0b 90 e9 46 fc ff ff e8 eb 3c c7 f6 90 <0f> 0b 90 4c 8b 24 24 e9 7c fe ff ff e8 d9 3c c7 f6 e9 2f fe ff ff
RSP: 0000:ffffc90004aff040 EFLAGS: 00010293
RAX: ffffffff8af86d55 RBX: dffffc0000000000 RCX: ffff88802bd2da00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffc90004aff0f0 R08: ffffc90004afede7 R09: 1ffff9200095fdbc
R10: dffffc0000000000 R11: fffff5200095fdbd R12: 0000000000000002
R13: ffff8880534569d0 R14: 1ffff1100a68ad3a R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff888125c28000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcb75946040 CR3: 000000007e27c000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ieee80211_do_stop+0xf47/0x1fb0 net/mac80211/iface.c:584
 ieee80211_stop+0x1b1/0x240 net/mac80211/iface.c:814
 __dev_close_many+0x361/0x6f0 net/core/dev.c:1755
 netif_close_many+0x225/0x410 net/core/dev.c:1780
 netif_close+0x158/0x210 net/core/dev.c:1797
 dev_close+0x10a/0x220 net/core/dev_api.c:220
 cfg80211_shutdown_all_interfaces+0xd4/0x220 net/wireless/core.c:277
 ieee80211_remove_interfaces+0x109/0x6e0 net/mac80211/iface.c:2364
 ieee80211_unregister_hw+0x5d/0x2c0 net/mac80211/main.c:1664
 mac80211_hwsim_del_radio+0x275/0x460 drivers/net/wireless/virtual/mac80211_hwsim.c:5674
 hwsim_exit_net+0x584/0x640 drivers/net/wireless/virtual/mac80211_hwsim.c:6554
 ops_exit_list net/core/net_namespace.c:198 [inline]
 ops_undo_list+0x497/0x990 net/core/net_namespace.c:251
 cleanup_net+0x4c5/0x800 net/core/net_namespace.c:682
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </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 syzkaller@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

                 reply	other threads:[~2025-08-09 10:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=68971e56.a70a0220.7865.0031.GAE@google.com \
    --to=syzbot+de3ee5362db09487ea37@syzkaller.appspotmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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.