From: syzbot <syzbot+319ed1769c0078257262@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, omosnace@redhat.com,
paul@paul-moore.com, selinux@vger.kernel.org,
stephen.smalley.work@gmail.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [selinux?] KCSAN: data-race in inode_doinit_with_dentry / selinux_file_open
Date: Fri, 23 Aug 2024 01:15:24 -0700 [thread overview]
Message-ID: <00000000000092a8070620556089@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: aa0743a22936 Merge tag 'net-6.11-rc5' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12609bd5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3aa0f597417bf8c7
dashboard link: https://syzkaller.appspot.com/bug?extid=319ed1769c0078257262
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e2399df8c24/disk-aa0743a2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/32d04570bb63/vmlinux-aa0743a2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/153aaf559bf9/bzImage-aa0743a2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+319ed1769c0078257262@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in inode_doinit_with_dentry / selinux_file_open
write to 0xffff888114a3392a of 1 bytes by task 5741 on cpu 0:
inode_doinit_with_dentry+0x29c/0x840 security/selinux/hooks.c:1443
__inode_security_revalidate security/selinux/hooks.c:295 [inline]
inode_security security/selinux/hooks.c:320 [inline]
selinux_file_open+0x101/0x3b0 security/selinux/hooks.c:3979
security_file_open+0x3a/0x70 security/security.c:2988
do_dentry_open+0x22e/0xa50 fs/open.c:946
vfs_open+0x3b/0x1f0 fs/open.c:1089
dentry_open+0x4a/0x90 fs/open.c:1112
pidfs_alloc_file+0xe6/0x150 fs/pidfs.c:404
__pidfd_prepare kernel/fork.c:2013 [inline]
pidfd_prepare+0xa0/0x120 kernel/fork.c:2074
pidfd_create kernel/pid.c:608 [inline]
__do_sys_pidfd_open kernel/pid.c:644 [inline]
__se_sys_pidfd_open+0x123/0x240 kernel/pid.c:629
__x64_sys_pidfd_open+0x31/0x40 kernel/pid.c:629
x64_sys_call+0x2873/0x2d60 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 0xffff888114a3392a of 1 bytes by task 5740 on cpu 1:
__inode_security_revalidate security/selinux/hooks.c:286 [inline]
inode_security security/selinux/hooks.c:320 [inline]
selinux_file_open+0xce/0x3b0 security/selinux/hooks.c:3979
security_file_open+0x3a/0x70 security/security.c:2988
do_dentry_open+0x22e/0xa50 fs/open.c:946
vfs_open+0x3b/0x1f0 fs/open.c:1089
dentry_open+0x4a/0x90 fs/open.c:1112
pidfs_alloc_file+0xe6/0x150 fs/pidfs.c:404
__pidfd_prepare kernel/fork.c:2013 [inline]
pidfd_prepare+0xa0/0x120 kernel/fork.c:2074
pidfd_create kernel/pid.c:608 [inline]
__do_sys_pidfd_open kernel/pid.c:644 [inline]
__se_sys_pidfd_open+0x123/0x240 kernel/pid.c:629
__x64_sys_pidfd_open+0x31/0x40 kernel/pid.c:629
x64_sys_call+0x2873/0x2d60 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: 1 UID: 0 PID: 5740 Comm: syz.0.725 Not tainted 6.11.0-rc4-syzkaller-00135-gaa0743a22936 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
==================================================================
netlink: 16 bytes leftover after parsing attributes in process `syz.0.725'.
---
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 syzkaller@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
reply other threads:[~2024-08-23 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000092a8070620556089@google.com \
--to=syzbot+319ed1769c0078257262@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox