[syzbot] [lsm?] WARNING in collect_domain_accesses (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 05c93f3395ed Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1077da1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3b5338ad1e59a06c
dashboard link: https://syzkaller.appspot.com/bug?extid=d818ec6483755ab6b0c0
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1518b992580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1212deb4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6b5c913e373c/disk-05c93f33.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/15e75f1266ef/vmlinux-05c93f33.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dd930129c578/Image-05c93f33.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6724 at security/landlock/fs.c:1066 collect_domain_accesses+0x208/0x258 security/landlock/fs.c:-1
Modules linked in:
CPU: 0 UID: 0 PID: 6724 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : collect_domain_accesses+0x208/0x258 security/landlock/fs.c:-1
lr : collect_domain_accesses+0x204/0x258 security/landlock/fs.c:1066
sp : ffff8000a0fc7830
x29: ffff8000a0fc7830 x28: ffff0000ed05d608 x27: ffff8000a0fc7c48
x26: ffff7000141f8f20 x25: dfff800000000000 x24: ffff0000ed01aeb0
x23: 0000000000002004 x22: ffff0000ed01aeb0 x21: ffff0000eb595700
x20: ffff0000ed05d608 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800082defd48 x15: 0000000000000001
x14: 0000000000000000 x13: 0000000000000002 x12: 0000000000ff0100
x11: ffff0000c66f0000 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c66f0000 x7 : ffff800082a23b24 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010
x2 : ffff8000a0fc7920 x1 : 0000000000002004 x0 : ffff0000ed01af00
Call trace:
collect_domain_accesses+0x208/0x258 security/landlock/fs.c:-1 (P)
current_check_refer_path+0x4e8/0xaec security/landlock/fs.c:1202
hook_path_rename+0x4c/0x60 security/landlock/fs.c:1524
security_path_rename+0x1dc/0x444 security/security.c:2065
do_renameat2+0x4b4/0x8a0 fs/namei.c:5352
__do_sys_renameat2 fs/namei.c:5398 [inline]
__se_sys_renameat2 fs/namei.c:5395 [inline]
__arm64_sys_renameat2+0xd8/0xf4 fs/namei.c:5395
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:724
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
irq event stamp: 2148
hardirqs last enabled at (2147): [<ffff800080dcd64c>] seqcount_lockdep_reader_access+0x7c/0xf8 include/linux/seqlock.h:74
hardirqs last disabled at (2148): [<ffff80008adf99f4>] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:412
softirqs last enabled at (1234): [<ffff8000803d9408>] softirq_handle_end kernel/softirq.c:468 [inline]
softirqs last enabled at (1234): [<ffff8000803d9408>] handle_softirqs+0xaf8/0xc88 kernel/softirq.c:650
softirqs last disabled at (1127): [<ffff800080022024>] __do_softirq+0x14/0x20 kernel/softirq.c:656
---[ end trace 0000000000000000 ]---


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

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