[moderation] [selinux?] KCSAN: data-race in inode_doinit_with_dentry / inode_doinit_with_dentry (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c4b9570cfb63 Merge tag 'audit-pr-20250121' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=172b49f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5869b5d3611ba
dashboard link: https://syzkaller.appspot.com/bug?extid=45113f4157790f28cc47
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org omos...@redhat.com pa...@paul-moore.com sel...@vger.kernel.org stephen.sm...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e618956dfad/disk-c4b9570c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76ee8d77c953/vmlinux-c4b9570c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/463f289c80da/bzImage-c4b9570c.xz

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

==================================================================
BUG: KCSAN: data-race in inode_doinit_with_dentry / inode_doinit_with_dentry

write to 0xffff888112265f82 of 1 bytes by task 7397 on cpu 1:
inode_doinit_with_dentry+0x29c/0x840 security/selinux/hooks.c:1448
__inode_security_revalidate security/selinux/hooks.c:300 [inline]
inode_security security/selinux/hooks.c:325 [inline]
selinux_file_open+0xff/0x3b0 security/selinux/hooks.c:3978
security_file_open+0x33/0x70 security/security.c:3104
do_dentry_open+0x1fa/0xa20 fs/open.c:921
vfs_open+0x38/0x1f0 fs/open.c:1068
dentry_open+0x4a/0x90 fs/open.c:1091
pidfs_alloc_file+0xe6/0x150 fs/pidfs.c:701
__pidfd_prepare kernel/fork.c:2030 [inline]
pidfd_prepare+0x5f/0xe0 kernel/fork.c:2078
pidfd_create kernel/pid.c:605 [inline]
__do_sys_pidfd_open kernel/pid.c:641 [inline]
__se_sys_pidfd_open+0x129/0x250 kernel/pid.c:626
__x64_sys_pidfd_open+0x31/0x40 kernel/pid.c:626
x64_sys_call+0x11b8/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:435
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888112265f82 of 1 bytes by task 7396 on cpu 0:
inode_doinit_with_dentry+0x78/0x840 security/selinux/hooks.c:1423
__inode_security_revalidate security/selinux/hooks.c:300 [inline]
inode_security security/selinux/hooks.c:325 [inline]
selinux_file_open+0xff/0x3b0 security/selinux/hooks.c:3978
security_file_open+0x33/0x70 security/security.c:3104
do_dentry_open+0x1fa/0xa20 fs/open.c:921
vfs_open+0x38/0x1f0 fs/open.c:1068
dentry_open+0x4a/0x90 fs/open.c:1091
pidfs_alloc_file+0xe6/0x150 fs/pidfs.c:701
__pidfd_prepare kernel/fork.c:2030 [inline]
pidfd_prepare+0x5f/0xe0 kernel/fork.c:2078
pidfd_create kernel/pid.c:605 [inline]
__do_sys_pidfd_open kernel/pid.c:641 [inline]
__se_sys_pidfd_open+0x129/0x250 kernel/pid.c:626
__x64_sys_pidfd_open+0x31/0x40 kernel/pid.c:626
x64_sys_call+0x11b8/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:435
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 7396 Comm: syz.4.29529 Not tainted 6.13.0-syzkaller-02526-gc4b9570cfb63 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
==================================================================


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