[Android 5.10] general protection fault in software_node_register

[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=10919149580000
kernel config: https://syzkaller.appspot.com/x/.config?x=57bdfa4a173e5087
dashboard link: https://syzkaller.appspot.com/bug?extid=7511221b30371b3818c8
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=1132cc79580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11963225580000

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+751122...@syzkaller.appspotmail.com

JBD2: Error while async write back metadata bh 33717.
sd 0:0:1:0: [sda] Synchronizing SCSI cache
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: 297 Comm: syz-executor314 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:software_node_register+0x36/0x1f0 drivers/base/swnode.c:800
Code: 53 48 83 ec 18 49 89 fe 48 bb 00 00 00 00 00 fc ff df e8 5d e9 b2 fe 4c 89 75 c8 4d 8d 66 08 4c 89 e0 48 c1 e8 03 48 89 45 c0 <80> 3c 18 00 74 08 4c 89 e7 e8 cc 5e ed fe 4d 8b 34 24 4d 85 f6 4c
RSP: 0018:ffffc90000b07770 EFLAGS: 00010202
RAX: 0000000000000001 RBX: dffffc0000000000 RCX: ffff88810ba913c0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b077b0 R08: ffff88810aec52bf R09: 1ffff110215d8a57
R10: dffffc0000000000 R11: ffffed10215d8a58 R12: 0000000000000008
R13: ffff88810b213010 R14: 0000000000000000 R15: 0000000000000000
FS: 000055558063e3c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd5f0fabb8 CR3: 00000001219fc000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
device_add_software_node+0x1ac/0x310 drivers/base/swnode.c:891
dwc3_pci_probe+0x397/0x980 drivers/usb/dwc3/dwc3-pci.c:286
local_pci_probe drivers/pci/pci-driver.c:308 [inline]
pci_call_probe drivers/pci/pci-driver.c:365 [inline]
__pci_device_probe drivers/pci/pci-driver.c:390 [inline]
pci_device_probe+0x27a/0x440 drivers/pci/pci-driver.c:433
really_probe+0x373/0xa60 drivers/base/dd.c:558
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:0x7fdf1051cdb9
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:00007ffdd0621eb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ffdd0621fe8 RCX: 00007fdf1051cdb9
RDX: 000000000000000d RSI: 0000200000000240 RDI: 0000000000000005
RBP: 0000000000000001 R08: 00007ffdd0621fe8 R09: 00007ffdd0621fe8
R10: 00007ffdd0621fe8 R11: 0000000000000246 R12: 00007ffdd0621fd8
R13: 0000000000000002 R14: 00007fdf105adca0 R15: 0000000000000002
Modules linked in:
---[ end trace 0b43e128b2a3bdc2 ]---
RIP: 0010:software_node_register+0x36/0x1f0 drivers/base/swnode.c:800
Code: 53 48 83 ec 18 49 89 fe 48 bb 00 00 00 00 00 fc ff df e8 5d e9 b2 fe 4c 89 75 c8 4d 8d 66 08 4c 89 e0 48 c1 e8 03 48 89 45 c0 <80> 3c 18 00 74 08 4c 89 e7 e8 cc 5e ed fe 4d 8b 34 24 4d 85 f6 4c
CR2: 00007ffd5f0fabb8 CR3: 00000001219fc000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 53 push %rbx
1: 48 83 ec 18 sub $0x18,%rsp
5: 49 89 fe mov %rdi,%r14
8: 48 bb 00 00 00 00 00 movabs $0xdffffc0000000000,%rbx
f: fc ff df
12: e8 5d e9 b2 fe call 0xfeb2e974
17: 4c 89 75 c8 mov %r14,-0x38(%rbp)
1b: 4d 8d 66 08 lea 0x8(%r14),%r12
1f: 4c 89 e0 mov %r12,%rax
22: 48 c1 e8 03 shr $0x3,%rax
26: 48 89 45 c0 mov %rax,-0x40(%rbp)
* 2a: 80 3c 18 00 cmpb $0x0,(%rax,%rbx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 4c 89 e7 mov %r12,%rdi
33: e8 cc 5e ed fe call 0xfeed5f04
38: 4d 8b 34 24 mov (%r12),%r14
3c: 4d 85 f6 test %r14,%r14
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