[moderation] [selinux?] KCSAN: data-race in ioctl_has_perm / selinux_inode_setsecurity

1 view
Skip to first unread message

syzbot

unread,
Feb 25, 2024, 1:52:19 PMFeb 25
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ab0a97cffa0b Merge tag 'powerpc-6.8-4' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b63522180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7507056e4ee79a
dashboard link: https://syzkaller.appspot.com/bug?extid=c3041582c537a89defab
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/786f1e630b29/disk-ab0a97cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0535b9d0e624/vmlinux-ab0a97cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2f3bbc61c7ec/bzImage-ab0a97cf.xz

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

==================================================================
BUG: KCSAN: data-race in ioctl_has_perm / selinux_inode_setsecurity

write to 0xffff888102e9cfb4 of 4 bytes by task 18209 on cpu 1:
selinux_inode_setsecurity+0x232/0x290 security/selinux/hooks.c:3489
security_inode_setsecurity+0x7f/0xc0 security/security.c:2537
__vfs_setxattr_noperm+0x149/0x3e0 fs/xattr.c:252
__vfs_setxattr_locked+0x1af/0x1d0 fs/xattr.c:296
vfs_setxattr+0x140/0x280 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
setxattr+0x1bc/0x230 fs/xattr.c:653
__do_sys_fsetxattr fs/xattr.c:709 [inline]
__se_sys_fsetxattr+0x117/0x170 fs/xattr.c:698
__x64_sys_fsetxattr+0x67/0x80 fs/xattr.c:698
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff888102e9cfb4 of 4 bytes by task 18208 on cpu 0:
ioctl_has_perm+0x262/0x2e0 security/selinux/hooks.c:3690
selinux_file_ioctl+0x2f2/0x380
security_file_ioctl+0x47/0x70 security/security.c:2726
__do_sys_ioctl fs/ioctl.c:865 [inline]
__se_sys_ioctl+0x47/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00000087 -> 0x000000a3

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 18208 Comm: syz-executor.1 Not tainted 6.8.0-rc5-syzkaller-00329-gab0a97cffa0b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/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

unread,
Mar 31, 2024, 2:52:12 PMMar 31
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages