[v6.1] BUG: unable to handle kernel paging request in scatterwalk_copychunks

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=166096d3280000
kernel config: https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link: https://syzkaller.appspot.com/bug?extid=f284950a44e32acbf81f
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000001
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000001] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 12135 Comm: kworker/u4:30 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Workqueue: pencrypt_parallel padata_parallel_worker
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : scatterwalk_start include/crypto/scatterwalk.h:63 [inline]
pc : scatterwalk_pagedone include/crypto/scatterwalk.h:83 [inline]
pc : scatterwalk_copychunks+0x3a8/0x558 crypto/scatterwalk.c:50
lr : scatterwalk_pagedone include/crypto/scatterwalk.h:83 [inline]
lr : scatterwalk_copychunks+0x384/0x558 crypto/scatterwalk.c:50
sp : ffff800020547520
x29: ffff800020547560 x28: 0000000000000000 x27: 0000000000000000
x26: 1ffff000040a8f20 x25: 0000000000000000 x24: 0000000000000008
x23: ffff800020547908 x22: 1ffff000040a8f21 x21: ffff800020547900
x20: 0000000000000001 x19: dfff800000000000 x18: ffff800020546f80
x17: ffff80000a78c294 x16: ffff800012054440 x15: ffff80000a78b00c
x14: ffff80000a78e9a4 x13: ffff80000802a8f8 x12: 0000000000000003
x11: ff8080000aa5d204 x10: 0000000000000000 x9 : ffff80000aa5d204
x8 : 0000000000000001 x7 : ffff80000896ca1c x6 : ffff800008969ee8
x5 : ffff0001496bdd00 x4 : ffff000000000000 x3 : ffff80000a7872ec
x2 : 0000000000000000 x1 : 0000000000000002 x0 : 0000000000000000
Call trace:
scatterwalk_start include/crypto/scatterwalk.h:63 [inline]
scatterwalk_pagedone include/crypto/scatterwalk.h:83 [inline]
scatterwalk_copychunks+0x3a8/0x558 crypto/scatterwalk.c:50
skcipher_next_slow+0x2e8/0x3c4 crypto/skcipher.c:278
skcipher_walk_next+0x544/0x9d8 crypto/skcipher.c:363
skcipher_walk_first crypto/skcipher.c:446 [inline]
skcipher_walk_aead_common+0x6f8/0xd08 crypto/skcipher.c:539
skcipher_walk_aead_encrypt+0x78/0xbc crypto/skcipher.c:552
gcm_encrypt+0x264/0x66c arch/arm64/crypto/ghash-ce-glue.c:363
crypto_aead_encrypt+0xb4/0xe0 crypto/aead.c:94
pcrypt_aead_enc+0x20/0x90 crypto/pcrypt.c:83
padata_parallel_worker+0x68/0x1bc kernel/padata.c:144
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: 9787974e 91002338 f90002b9 d343ff08 (38f36908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 9787974e bl 0xfffffffffe1e5d38
4: 91002338 add x24, x25, #0x8
8: f90002b9 str x25, [x21]
c: d343ff08 lsr x8, x24, #3
* 10: 38f36908 ldrsb w8, [x8, x19] <-- 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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.