[v5.15] BUG: unable to handle kernel paging request in hook_inode_free_security

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11cc0ebc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ea6d61094f2bc7
dashboard link: https://syzkaller.appspot.com/bug?extid=0371303dd168d73b8f64
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5b3869563672/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/382d7f427d53/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c344c3ce2e27/Image-1c700860.gz.xz

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

Unable to handle kernel paging request at virtual address dfff8001bcd01f33
Mem abort info:
ESR = 0x0000000096000005
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x05: level 1 translation fault
Data abort info:
ISV = 0, ISS = 0x00000005
CM = 0, WnR = 0
[dfff8001bcd01f33] address between user and kernel address ranges
Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4026 Comm: syz-executor Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hook_inode_free_security+0x60/0xc4 security/landlock/fs.c:408
lr : hook_inode_free_security+0x20/0xc4 security/landlock/fs.c:403
sp : ffff80001f2074a0
x29: ffff80001f2074a0 x28: 1fffe0001e3be8d0 x27: dfff800000000000
x26: ffff700003e40eb0 x25: 1fffe0001e3be8d3 x24: dfff800000000000
x23: ffff0000f1df4680 x22: ffff0000cc34a060 x21: dfff800000000000
x20: dfff800000000000 x19: 0000000de680f998 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082d4c48 x15: 0000000000000406
x14: 0000000000ff0100 x13: 1ffff0000282c06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff80000a453a0c
x8 : 00000001bcd01f33 x7 : ffff800008959254 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d4d5c
x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff0000f1df44f0
Call trace:
hook_inode_free_security+0x60/0xc4 security/landlock/fs.c:408
security_inode_free+0x58/0xd8 security/security.c:1054
__destroy_inode+0x2f0/0x80c fs/inode.c:286
destroy_inode fs/inode.c:309 [inline]
evict+0x6b0/0x810 fs/inode.c:662
dispose_list fs/inode.c:680 [inline]
evict_inodes+0x64c/0x6e4 fs/inode.c:734
generic_shutdown_super+0x9c/0x2f0 fs/super.c:454
kill_block_super+0x70/0xdc fs/super.c:1427
deactivate_locked_super+0xb8/0x13c fs/super.c:335
deactivate_super+0xf8/0x118 fs/super.c:366
cleanup_mnt+0x3a4/0x458 fs/namespace.c:1139
__cleanup_mnt+0x20/0x30 fs/namespace.c:1146
task_work_run+0x12c/0x1e0 kernel/task_work.c:188
exit_task_work include/linux/task_work.h:33 [inline]
do_exit+0x67c/0x1f58 kernel/exit.c:874
do_group_exit+0x100/0x268 kernel/exit.c:996
get_signal+0x73c/0x1340 kernel/signal.c:2900
do_signal arch/arm64/kernel/signal.c:893 [inline]
do_notify_resume+0x35c/0x3128 arch/arm64/kernel/signal.c:946
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xf0/0x1e0 arch/arm64/kernel/entry-common.c:609
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: f004b7a8 b986b508 8b080273 d343fe68 (38746908)
---[ end trace 0246128db1424601 ]---
----------------
Code disassembly (best guess):
0: f004b7a8 adrp x8, 0x96f7000
4: b986b508 ldrsw x8, [x8, #1716]
8: 8b080273 add x19, x19, x8
c: d343fe68 lsr x8, x19, #3
* 10: 38746908 ldrb w8, [x8, x20] <-- 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]

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