[v6.6] kernel BUG in lookup_or_create_module_kobject

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a91a6aa9253c Linux 6.6.158
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10918f15580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57b328ed0f39e7
dashboard link: https://syzkaller.appspot.com/bug?extid=53326e6b5b200e83ab04
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/9b21ee9eea32/disk-a91a6aa9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/464d9e3ba874/vmlinux-a91a6aa9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c730562b3d82/bzImage-a91a6aa9.xz

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

RBP: 00007f0976a3efd0 R08: 0000000000000001 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000200000002000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
------------[ cut here ]------------
kernel BUG at kernel/params.c:759!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5877 Comm: syz.3.11 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:lookup_or_create_module_kobject+0x15c/0x160 kernel/params.c:759
Code: eb 05 e8 97 54 2d 00 4c 89 f7 e8 7f 94 24 09 48 c7 c7 80 2e ca 8a 48 89 de 89 ea e8 4e 47 2d 09 45 31 f6 eb c8 e8 74 54 2d 00 <0f> 0b 66 90 f3 0f 1e fa 41 56 53 48 89 d3 49 89 fe e8 5e 54 2d 00
RSP: 0018:ffffc9000497fa48 EFLAGS: 00010246
RAX: ffffffff815a3c3c RBX: ffffffff8b7e4c40 RCX: 0000000000080000
RDX: ffffc9000d27a000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: dffffc0000000000 R08: 0000000000000080 R09: 1ffffffff1c0602e
R10: dffffc0000000000 R11: fffffbfff1c0602f R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88802668a098
FS: 00007f0976a406c0(0000) GS:ffff8880b8d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f31f552fff8 CR3: 000000005b7de000 CR4: 00000000003506e0
Call Trace:
<TASK>
module_add_driver+0x79/0x320 drivers/base/module.c:46
bus_add_driver+0x38c/0x630 drivers/base/bus.c:727
driver_register+0x23a/0x310 drivers/base/driver.c:246
usb_gadget_register_driver_owner+0xf9/0x270 drivers/usb/gadget/udc/core.c:1735
raw_ioctl_run drivers/usb/gadget/legacy/raw_gadget.c:549 [inline]
raw_ioctl+0x1613/0x3d80 drivers/usb/gadget/legacy/raw_gadget.c:1262
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0975b9de6b
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
RSP: 002b:00007f0976a3df00 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007f0975b9de6b
RDX: 0000000000000000 RSI: 0000000000005501 RDI: 0000000000000007
RBP: 00007f0976a3efd0 R08: 0000000000000001 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000200000002000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:

---[ end trace 0000000000000000 ]---
RIP: 0010:lookup_or_create_module_kobject+0x15c/0x160 kernel/params.c:759
Code: eb 05 e8 97 54 2d 00 4c 89 f7 e8 7f 94 24 09 48 c7 c7 80 2e ca 8a 48 89 de 89 ea e8 4e 47 2d 09 45 31 f6 eb c8 e8 74 54 2d 00 <0f> 0b 66 90 f3 0f 1e fa 41 56 53 48 89 d3 49 89 fe e8 5e 54 2d 00
RSP: 0018:ffffc9000497fa48 EFLAGS: 00010246

RAX: ffffffff815a3c3c RBX: ffffffff8b7e4c40 RCX: 0000000000080000
RDX: ffffc9000d27a000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: dffffc0000000000 R08: 0000000000000080 R09: 1ffffffff1c0602e
R10: dffffc0000000000 R11: fffffbfff1c0602f R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88802668a098
FS: 00007f0976a406c0(0000) GS:ffff8880b8d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f31f4587340 CR3: 000000005b7de000 CR4: 00000000003506e0


---
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