[Android 5.10] general protection fault in usb_driver_release_interface

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 452567d1985b Revert "HID: input: read battery capacity fro..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13ade3f9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57bdfa4a173e5087
dashboard link: https://syzkaller.appspot.com/bug?extid=9af6cc4c39da57aec654
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ddfdf9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165818c9580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9268e34b0c5f/disk-452567d1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7237143009db/vmlinux-452567d1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2921bc70b2f7/bzImage-452567d1.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000004: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
CPU: 1 PID: 20 Comm: kworker/1:0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del lib/klist.c:230 [inline]
RIP: 0010:klist_remove+0x150/0x300 lib/klist.c:249
Code: 28 02 49 89 df 49 c1 ef 03 43 80 3c 27 00 74 08 48 89 df e8 a2 5d 45 ff 4c 8b 33 49 83 e6 fe 49 8d 7e 20 48 89 f8 48 c1 e8 03 <42> 80 3c 20 00 74 05 e8 84 5d 45 ff 49 8b 46 20 48 89 44 24 18 4c
RSP: 0018:ffffc90000157480 EFLAGS: 00010202
RAX: 0000000000000004 RBX: ffff88810deeb848 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8676fae0 RDI: 0000000000000020
RBP: ffffc90000157570 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200002ae80 R12: dffffc0000000000
R13: 1ffff9200002ae94 R14: 0000000000000000 R15: 1ffff11021bdd709
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000559e79618300 CR3: 000000010b1e0000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__device_release_driver drivers/base/dd.c:1203 [inline]
device_release_driver_internal+0x67e/0x7c0 drivers/base/dd.c:1221
device_release_driver+0x19/0x20 drivers/base/dd.c:1244
usb_driver_release_interface+0x140/0x1b0 drivers/usb/core/driver.c:632
cdc_ncm_unbind+0x2b3/0x440 drivers/net/usb/cdc_ncm.c:1001
cdc_mbim_unbind+0xec/0x100 drivers/net/usb/cdc_mbim.c:205
usbnet_disconnect+0x1a9/0x3a0 drivers/net/usb/usbnet.c:1611
usb_unbind_interface+0x212/0x8a0 drivers/usb/core/driver.c:459
__device_release_driver drivers/base/dd.c:-1 [inline]
device_release_driver_internal+0x531/0x7c0 drivers/base/dd.c:1221
device_release_driver+0x19/0x20 drivers/base/dd.c:1244
bus_remove_device+0x2df/0x340 drivers/base/bus.c:535
device_del+0x62e/0xe60 drivers/base/core.c:3453
usb_disable_device+0x3a8/0x750 drivers/usb/core/message.c:1470
usb_disconnect+0x32d/0x870 drivers/usb/core/hub.c:2315
hub_port_connect drivers/usb/core/hub.c:5343 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5644 [inline]
port_event drivers/usb/core/hub.c:5810 [inline]
hub_event+0x19c2/0x4220 drivers/usb/core/hub.c:5892
process_one_work+0x6fd/0xbc0 kernel/workqueue.c:2301
worker_thread+0xa8e/0x13c0 kernel/workqueue.c:2447
kthread+0x324/0x3b0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Modules linked in:
---[ end trace 7387eebc842e211d ]---
RIP: 0010:klist_put lib/klist.c:212 [inline]
RIP: 0010:klist_del lib/klist.c:230 [inline]
RIP: 0010:klist_remove+0x150/0x300 lib/klist.c:249
Code: 28 02 49 89 df 49 c1 ef 03 43 80 3c 27 00 74 08 48 89 df e8 a2 5d 45 ff 4c 8b 33 49 83 e6 fe 49 8d 7e 20 48 89 f8 48 c1 e8 03 <42> 80 3c 20 00 74 05 e8 84 5d 45 ff 49 8b 46 20 48 89 44 24 18 4c
RSP: 0018:ffffc90000157480 EFLAGS: 00010202
RAX: 0000000000000004 RBX: ffff88810deeb848 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8676fae0 RDI: 0000000000000020
RBP: ffffc90000157570 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200002ae80 R12: dffffc0000000000
R13: 1ffff9200002ae94 R14: 0000000000000000 R15: 1ffff11021bdd709
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe729dc688 CR3: 000000010d597000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 28 02 sub %al,(%rdx)
2: 49 89 df mov %rbx,%r15
5: 49 c1 ef 03 shr $0x3,%r15
9: 43 80 3c 27 00 cmpb $0x0,(%r15,%r12,1)
e: 74 08 je 0x18
10: 48 89 df mov %rbx,%rdi
13: e8 a2 5d 45 ff call 0xff455dba
18: 4c 8b 33 mov (%rbx),%r14
1b: 49 83 e6 fe and $0xfffffffffffffffe,%r14
1f: 49 8d 7e 20 lea 0x20(%r14),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 05 je 0x36
31: e8 84 5d 45 ff call 0xff455dba
36: 49 8b 46 20 mov 0x20(%r14),%rax
3a: 48 89 44 24 18 mov %rax,0x18(%rsp)
3f: 4c rex.WR


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