Hello,
syzbot found the following issue on:
HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11e7acc6580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link:
https://syzkaller.appspot.com/bug?extid=31ec6bc3a92b8aa9f2f7
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+31ec6b...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4365 at drivers/net/wireless/ath/ath10k/pci.c:3599 ath10k_pci_probe+0x117/0x18c0 drivers/net/wireless/ath/ath10k/pci.c:3599
Modules linked in:
CPU: 0 PID: 4365 Comm: kworker/0:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events work_for_cpu_fn
RIP: 0010:ath10k_pci_probe+0x117/0x18c0 drivers/net/wireless/ath/ath10k/pci.c:3599
Code: 44 24 20 90 8b eb 85 48 c7 44 24 18 10 7c eb 85 b0 01 89 44 24 14 31 c9 c7 44 24 30 00 00 00 00 e9 2b 01 00 00 e8 29 cc 96 fb <0f> 0b 41 bf f4 fd ff ff 48 8b 5c 24 50 e9 f0 06 00 00 e8 12 cc 96
RSP: 0018:ffffc90004427ae0 EFLAGS: 00010293
RAX: ffffffff85eb61f7 RBX: 00000000ffffffff RCX: ffff88802f7e5a00
RDX: 0000000000000000 RSI: ffffffff8d607a10 RDI: 00000000ffffffff
RBP: ffffc90004427bd0 R08: ffff88802f7e5a00 R09: 0000000000000009
R10: 00000000000011ac R11: 0000000000000000 R12: ffffffff8ae3a584
R13: ffffc90004427b60 R14: 1ffffffff15c74b0 R15: ffff8881432fa000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3dfd8c CR3: 00000000567d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
local_pci_probe+0xc5/0x150 drivers/pci/pci-driver.c:324
work_for_cpu_fn+0x50/0x80 kernel/workqueue.c:5184
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 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