[Android 5.10] general protection fault in acpi_fan_probe

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e334a66065d3 Merge 5.10.264 into android13-5.10-lts
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=101ad6c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57bdfa4a173e5087
dashboard link: https://syzkaller.appspot.com/bug?extid=36752dd09e1c852fd2e3
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=1173fa79580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1757da79580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e40f9bd31ba6/disk-e334a660.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ff25a46f2c72/vmlinux-e334a660.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81f10a152c93/bzImage-e334a660.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000051: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000288-0x000000000000028f]
CPU: 0 PID: 297 Comm: syz-executor310 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:acpi_fan_probe+0x10e/0x1030 drivers/acpi/fan.c:387
Code: 84 fc 04 00 00 49 89 c6 4c 89 64 24 30 4c 89 7c 24 48 4c 8d bb 88 02 00 00 4d 89 fc 49 c1 ec 03 48 b8 00 00 00 00 00 fc ff df <41> 80 3c 04 00 74 08 4c 89 ff e8 33 d2 20 ff 4c 89 7c 24 20 4d 89
RSP: 0018:ffffc90000b87820 EFLAGS: 00010202

RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000a02 RDI: 00000000ffffffff
RBP: ffffc90000b879e0 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000170ee4 R12: 0000000000000051
R13: 1ffff92000170f14 R14: ffff88810aca8018 R15: 0000000000000288
FS: 00005555571fb3c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000004 CR3: 000000010aafd000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
platform_drv_probe+0x11b/0x1a0 drivers/base/platform.c:761
really_probe+0x3bf/0xa60 drivers/base/dd.c:562
driver_probe_device+0xe1/0x190 drivers/base/dd.c:752
device_driver_attach+0x17a/0x280 drivers/base/dd.c:1035
bind_store+0x369/0x3c0 drivers/base/bus.c:216
drv_attr_store+0x79/0xa0 drivers/base/bus.c:77
sysfs_kf_write+0x129/0x150 fs/sysfs/file.c:143
kernfs_fop_write_iter+0x2bd/0x400 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2066 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0x770/0xd70 fs/read_write.c:605
ksys_write+0x14a/0x260 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:667
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1392f93cf9
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 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 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3bc73348 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000200000000000 RCX: 00007f1392f93cf9
RDX: 0000000000000007 RSI: 0000200000000800 RDI: 0000000000000004
RBP: 0000000000000001 R08: 00007fff3bc73478 R09: 00007fff3bc73478
R10: 00007fff3bc73478 R11: 0000000000000246 R12: 00007fff3bc73468
R13: 0000000000000002 R14: 00007f1393024ca0 R15: 0000000000000002
Modules linked in:
---[ end trace 0216b48cfdaa9b0b ]---
RIP: 0010:acpi_fan_probe+0x10e/0x1030 drivers/acpi/fan.c:387
Code: 84 fc 04 00 00 49 89 c6 4c 89 64 24 30 4c 89 7c 24 48 4c 8d bb 88 02 00 00 4d 89 fc 49 c1 ec 03 48 b8 00 00 00 00 00 fc ff df <41> 80 3c 04 00 74 08 4c 89 ff e8 33 d2 20 ff 4c 89 7c 24 20 4d 89
RSP: 0018:ffffc90000b87820 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000a02 RDI: 00000000ffffffff
RBP: ffffc90000b879e0 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000170ee4 R12: 0000000000000051
R13: 1ffff92000170f14 R14: ffff88810aca8018 R15: 0000000000000288
FS: 00005555571fb3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006a9ee0 CR3: 000000010aafd000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 3 bytes skipped:
0: 00 00 add %al,(%rax)
2: 49 89 c6 mov %rax,%r14
5: 4c 89 64 24 30 mov %r12,0x30(%rsp)
a: 4c 89 7c 24 48 mov %r15,0x48(%rsp)
f: 4c 8d bb 88 02 00 00 lea 0x288(%rbx),%r15
16: 4d 89 fc mov %r15,%r12
19: 49 c1 ec 03 shr $0x3,%r12
1d: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
24: fc ff df
* 27: 41 80 3c 04 00 cmpb $0x0,(%r12,%rax,1) <-- trapping instruction
2c: 74 08 je 0x36
2e: 4c 89 ff mov %r15,%rdi
31: e8 33 d2 20 ff call 0xff20d269
36: 4c 89 7c 24 20 mov %r15,0x20(%rsp)
3b: 4d rex.WRB
3c: 89 .byte 0x89


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