[v6.1] Unable to handle kernel write to read-only memory at virtual address ADDR

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c242b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=ae1270b70f324f75ac92
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.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/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz

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

Unable to handle kernel write to read-only memory at virtual address ffff0000db87b044
KASAN: maybe wild-memory-access in range [0xfffc0006dc3d8220-0xfffc0006dc3d8227]
Mem abort info:
ESR = 0x000000009600004f
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x0f: level 3 permission fault
Data abort info:
ISV = 0, ISS = 0x0000004f
CM = 0, WnR = 1
swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000020e268000
[ffff0000db87b044] pgd=180000023fff7003, p4d=180000023fff7003, pud=180000023f413003, pmd=180000023f336003, pte=006000011b87b787
Internal error: Oops: 000000009600004f [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 6178 Comm: syz.3.261 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __memcpy+0x1b4/0x260 arch/arm64/lib/memcpy.S:206
lr : memmove+0x74/0x90 mm/kasan/shadow.c:58
sp : ffff800021c07440
x29: ffff800021c07440 x28: 0000000000000000 x27: ffff0000db879000
x26: ffff0000db87904c x25: dfff800000000000 x24: 00000000000003cc
x23: 0000000000000800 x22: ffff800008caa8dc x21: ffff0000db879058
x20: ffff0000db879050 x19: 0000000000001ffc x18: ffff800011abbcc0
x17: 00000fe800000218 x16: ffff8000082d25ac x15: ffff8000089a0ae0
x14: 0000000000000004 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: ffff60001b70f60b x9 : 0000000000000000
x8 : 0000000000000001 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff0000db87b054 x4 : ffff0000db87b048 x3 : ffff800008caa8dc
x2 : 0000000000001ff8 x1 : ffff0000db879050 x0 : ffff0000db879058
Call trace:
__memcpy+0x1b4/0x260 arch/arm64/lib/memcpy.S:205
reiserfs_release_objectid+0x430/0x614 fs/reiserfs/objectid.c:165
remove_save_link+0x21c/0x320 fs/reiserfs/super.c:542
reiserfs_evict_inode+0x2f8/0x3e4 fs/reiserfs/inode.c:91
evict+0x3c8/0x810 fs/inode.c:705
iput_final fs/inode.c:1834 [inline]
iput+0x764/0x7f4 fs/inode.c:1860
dentry_unlink_inode+0x360/0x438 fs/dcache.c:405
__dentry_kill+0x320/0x598 fs/dcache.c:611
dentry_kill+0xc8/0x248 fs/dcache.c:-1
dput+0x238/0x454 fs/dcache.c:918
__fput+0x480/0x7c0 fs/file_table.c:328
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x1ec/0x270 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2038/0x2b28 arch/arm64/kernel/signal.c:1137
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x98/0x138 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 92400cae cb0e0084 cb0e0042 a97f1c86 (a93f34ac)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 92400cae and x14, x5, #0xf
4: cb0e0084 sub x4, x4, x14
8: cb0e0042 sub x2, x2, x14
c: a97f1c86 ldp x6, x7, [x4, #-16]
* 10: a93f34ac stp x12, x13, [x5, #-16] <-- 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