[v6.6] general protection fault in ucsi_acpi_probe

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d27334b2888c Linux 6.6.151
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15492679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0bc3d90c30838b5
dashboard link: https://syzkaller.appspot.com/bug?extid=172e67a4ad8a227efa45
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/695139abd971/disk-d27334b2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b11fc121442a/vmlinux-d27334b2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e226f54f9286/bzImage-d27334b2.xz

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

general protection fault, probably for non-canonical address 0xdffffc00000000e3: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000718-0x000000000000071f]
CPU: 1 PID: 6273 Comm: syz.5.101 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:ucsi_acpi_probe+0x6c/0x500 drivers/usb/typec/ucsi/ucsi_acpi.c:223
Code: 89 74 24 08 4c 8b 23 4c 89 e7 e8 9f 24 a4 fd 49 83 c4 f0 45 31 f6 84 c0 4d 0f 45 f4 49 81 c6 1c 07 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 47 04 00 00 41 8b 2e 31 ff 89 ee e8 6b
RSP: 0018:ffffc9000b71fb08 EFLAGS: 00010203
RAX: 00000000000000e3 RBX: ffff8881416fe420 RCX: 0000000000080000
RDX: ffffc9001bcee000 RSI: 0000000000000987 RDI: 0000000000000988
RBP: 0000000000000000 R08: ffff888144f456cb R09: 1ffff110289e8ad9
R10: dffffc0000000000 R11: ffffed10289e8ada R12: fffffffffffffff0
R13: dffffc0000000000 R14: 000000000000071c R15: 1ffff110282dfc84
FS: 00007efefa39d6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3fbfc0 CR3: 000000004fd5d000 CR4: 00000000003506e0
Call Trace:
<TASK>
platform_probe+0x13b/0x1c0 drivers/base/platform.c:1376
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x247/0xae0 drivers/base/dd.c:717
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:879
device_driver_attach+0xe0/0x1d0 drivers/base/dd.c:1206
bind_store+0x1cc/0x210 drivers/base/bus.c:267
kernfs_fop_write_iter+0x3a4/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x474/0x9a0 fs/read_write.c:584
ksys_write+0x151/0x260 fs/read_write.c:637
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:0x7efef959e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efefa39d028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007efef9825fa0 RCX: 00007efef959e0d9
RDX: 0000000000000006 RSI: 00002000000001c0 RDI: 0000000000000003
RBP: 00007efef9635024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007efef9826038 R14: 00007efef9825fa0 R15: 00007ffdbb52aa58
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
Code: 89 74 24 08 4c 8b 23 4c 89 e7 e8 9f 24 a4 fd 49 83 c4 f0 45 31 f6 84 c0 4d 0f 45 f4 49 81 c6 1c 07 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 47 04 00 00 41 8b 2e 31 ff 89 ee e8 6b
RSP: 0018:ffffc9000b71fb08 EFLAGS: 00010203
RAX: 00000000000000e3 RBX: ffff8881416fe420 RCX: 0000000000080000
RDX: ffffc9001bcee000 RSI: 0000000000000987 RDI: 0000000000000988
RBP: 0000000000000000 R08: ffff888144f456cb R09: 1ffff110289e8ad9
R10: dffffc0000000000 R11: ffffed10289e8ada R12: fffffffffffffff0
R13: dffffc0000000000 R14: 000000000000071c R15: 1ffff110282dfc84
FS: 00007efefa39d6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd671c8fff8 CR3: 000000004fd5d000 CR4: 00000000003506f0
----------------
Code disassembly (best guess):
0: 89 74 24 08 mov %esi,0x8(%rsp)
4: 4c 8b 23 mov (%rbx),%r12
7: 4c 89 e7 mov %r12,%rdi
a: e8 9f 24 a4 fd call 0xfda424ae
f: 49 83 c4 f0 add $0xfffffffffffffff0,%r12
13: 45 31 f6 xor %r14d,%r14d
16: 84 c0 test %al,%al
18: 4d 0f 45 f4 cmovne %r12,%r14
1c: 49 81 c6 1c 07 00 00 add $0x71c,%r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 47 04 00 00 jne 0x47e
37: 41 8b 2e mov (%r14),%ebp
3a: 31 ff xor %edi,%edi
3c: 89 ee mov %ebp,%esi
3e: e8 .byte 0xe8
3f: 6b .byte 0x6b


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