Hello,
syzbot found the following issue on:
HEAD commit: 6e2fd6534337 Linux 5.15.213
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=173d13b9580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link:
https://syzkaller.appspot.com/bug?extid=46e393fe0ffd5b550bca
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/d7b46606b13d/disk-6e2fd653.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/da120fdeb081/vmlinux-6e2fd653.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3c2643457e3f/bzImage-6e2fd653.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+46e393...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 1347 Comm: kworker/0:3 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:software_node_register+0x2c/0x1e0 drivers/base/swnode.c:957
Code: 57 41 56 41 55 41 54 53 50 48 89 fb 49 be 00 00 00 00 00 fc ff df e8 c3 e9 9c fc 4c 8d 63 08 4c 89 e0 48 c1 e8 03 48 89 04 24 <42> 80 3c 30 00 74 08 4c 89 e7 e8 65 0c e2 fc 49 8b 2c 24 48 85 ed
RSP: 0018:ffffc900049c7a00 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffff888023048000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900049c7bd0 R08: ffff88805b171e7f R09: 1ffff1100b62e3cf
R10: dffffc0000000000 R11: ffffed100b62e3d0 R12: 0000000000000008
R13: ffff88807779f010 R14: dffffc0000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c364c54 CR3: 0000000058753000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
device_add_software_node+0x19c/0x2f0 drivers/base/swnode.c:1045
dwc3_pci_quirks drivers/usb/dwc3/dwc3-pci.c:263 [inline]
dwc3_pci_probe+0x52a/0x970 drivers/usb/dwc3/dwc3-pci.c:328
local_pci_probe+0xc5/0x150 drivers/pci/pci-driver.c:323
work_for_cpu_fn+0x50/0x80 kernel/workqueue.c:5217
process_one_work+0x867/0xff0 kernel/workqueue.c:2310
worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
Dumping ftrace buffer:
(ftrace buffer empty)
CR2: 000000110c364c54 CR3: 0000000058be1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 57 push %rdi
1: 41 56 push %r14
3: 41 55 push %r13
5: 41 54 push %r12
7: 53 push %rbx
8: 50 push %rax
9: 48 89 fb mov %rdi,%rbx
c: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14
13: fc ff df
16: e8 c3 e9 9c fc call 0xfc9ce9de
1b: 4c 8d 63 08 lea 0x8(%rbx),%r12
1f: 4c 89 e0 mov %r12,%rax
22: 48 c1 e8 03 shr $0x3,%rax
26: 48 89 04 24 mov %rax,(%rsp)
* 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 e7 mov %r12,%rdi
34: e8 65 0c e2 fc call 0xfce20c9e
39: 49 8b 2c 24 mov (%r12),%rbp
3d: 48 85 ed test %rbp,%rbp
---
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