[v5.15] Internal error in snapshot_ioctl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c932f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=d113fb2cfec542c4370e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5455 Comm: syz.0.617 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : snapshot_ioctl+0x7b4/0xdd8 kernel/power/user.c:368
lr : snapshot_ioctl+0x790/0xdd8 kernel/power/user.c:355
sp : ffff800020067ce0
x29: ffff800020067ce0 x28: ffff0000d4fc1b40 x27: 0000000000000003
x26: 1fffe0001a9f8368 x25: dfff800000000000 x24: 0000000000003300
x23: dfff800000000000 x22: 0000000000400140 x21: 0000000000000000
x20: 00000000fffffff2 x19: 0000000000000000 x18: 0000000000000000
x17: ffff800016d04000 x16: ffff8000082efca8 x15: ffff8000167e4500
x14: ffff0000d4fc2540 x13: dfff800000000000 x12: 0000000000080000
x11: 0000000000000000 x10: 0000ffffffffffff x9 : 0000000000000000
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800016f60d58 x4 : 0000000000000008 x3 : ffff8000082bfb8c
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
snapshot_ioctl+0x7b4/0xdd8 kernel/power/user.c:357
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: ea2a011f 9a9f026b d503229f f8000969 (140000b2)
---[ end trace 2548f052f1051251 ]---
----------------
Code disassembly (best guess):
0: ea2a011f bics xzr, x8, x10
4: 9a9f026b csel x11, x19, xzr, eq // eq = none
8: d503229f csdb
c: f8000969 sttr x9, [x11]
* 10: 140000b2 b 0x2d8 <-- trapping instruction


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1490f1a2580000

kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=d113fb2cfec542c4370e
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1290f1a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=153129a2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4215 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : snapshot_ioctl+0x7b4/0xdd8 kernel/power/user.c:368
lr : snapshot_ioctl+0x790/0xdd8 kernel/power/user.c:355

sp : ffff80001fb47ce0
x29: ffff80001fb47ce0 x28: ffff0000d76a3680 x27: 0000000000000003
x26: 1fffe0001aed46d0 x25: dfff800000000000 x24: 0000000000003300

x23: dfff800000000000 x22: 0000000000400140 x21: 0000000000000000
x20: 00000000fffffff2 x19: 0000000000000000 x18: 0000000000000000
x17: ffff800016d04000 x16: ffff8000082efca8 x15: ffff8000167e4500

x14: ffff0000d76a4080 x13: dfff800000000000 x12: 0000000000ff0100

x11: 0000000000000000 x10: 0000ffffffffffff x9 : 0000000000000000
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000

x5 : ffff800016ea4120 x4 : 0000000000000008 x3 : ffff8000082bfb8c

x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
snapshot_ioctl+0x7b4/0xdd8 kernel/power/user.c:357
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: ea2a011f 9a9f026b d503229f f8000969 (140000b2)

---[ end trace b156e8309790bda6 ]---

----------------
Code disassembly (best guess):
0: ea2a011f bics xzr, x8, x10
4: 9a9f026b csel x11, x19, xzr, eq // eq = none
8: d503229f csdb
c: f8000969 sttr x9, [x11]
* 10: 140000b2 b 0x2d8 <-- trapping instruction


---

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.