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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=104c7649580000
kernel config: https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link: https://syzkaller.appspot.com/bug?extid=2b8d9eb788ea61056172
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d420eb944682/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/affae450ab23/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b9e6919ed519/Image-fb28aa72.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000013
KASAN: null-ptr-deref in range [0x0000000000000098-0x000000000000009f]
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
[dfff800000000013] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4374 Comm: kworker/0:4 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
Workqueue: kafsd afs_process_async_call
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __mutex_lock_common+0xfc/0x1f3c kernel/locking/mutex.c:582
lr : __mutex_lock_common+0xd0/0x1f3c kernel/locking/mutex.c:580
sp : ffff800020e478a0
x29: ffff800020e479e0 x28: ffff7000041c8f28 x27: 0000000000000000
x26: 0000000000000000 x25: 1fffe000199b9600 x24: 0000000000000000
x23: dfff800000000000 x22: ffff800010fd8f18 x21: ffff800020e47960
x20: 0000000000000000 x19: 0000000000000038 x18: 1fffe00033e7277e
x17: ffff80001537d000 x16: ffff8000082dbd3c x15: 0000000000000000
x14: 0000000000000005 x13: 1ffff000041c8f2c x12: 0000000000000000
x11: ff0080000a975dac x10: 0000000000000000 x9 : 0000000000000003
x8 : 0000000000000013 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000000 x1 : ffff800011ceedc0 x0 : 0000000000000000
Call trace:
__mutex_lock_common+0xfc/0x1f3c kernel/locking/mutex.c:582
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
rxrpc_kernel_abort_call+0x34/0x88 net/rxrpc/sendmsg.c:853
afs_deliver_to_call+0x4d0/0xec0 fs/afs/rxrpc.c:-1
afs_process_async_call+0x90/0xf8 fs/afs/rxrpc.c:703
process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292
worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439
kthread+0x254/0x2e0 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: b9486108 35000148 91018268 d343fd08 (38776908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: b9486108 ldr w8, [x8, #2144]
4: 35000148 cbnz w8, 0x2c
8: 91018268 add x8, x19, #0x60
c: d343fd08 lsr x8, x8, #3
* 10: 38776908 ldrb w8, [x8, x23] <-- 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: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=123a93b9580000

kernel config: https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link: https://syzkaller.appspot.com/bug?extid=2b8d9eb788ea61056172
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115f4bb9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e46cc6580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d420eb944682/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/affae450ab23/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b9e6919ed519/Image-fb28aa72.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000013
KASAN: null-ptr-deref in range [0x0000000000000098-0x000000000000009f]
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
[dfff800000000013] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:

CPU: 0 PID: 4430 Comm: kworker/0:12 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
Workqueue: kafsd afs_process_async_call
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __mutex_lock_common+0xfc/0x1f3c kernel/locking/mutex.c:582
lr : __mutex_lock_common+0xd0/0x1f3c kernel/locking/mutex.c:580

sp : ffff800020f878a0
x29: ffff800020f879e0 x28: ffff7000041f0f28 x27: 0000000000000000
x26: 0000000000000000 x25: 1fffe0001e7df800 x24: 0000000000000000
x23: dfff800000000000 x22: ffff800010fd8f18 x21: ffff800020f87960
x20: 0000000000000000 x19: 0000000000000038 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082dbd3c x15: 0000000000000000
x14: 0000000000000005 x13: 1ffff000041f0f2c x12: 0000000000000000

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.