[moderation] [lsm?] [keyrings?] KCSAN: data-race in __se_sys_keyctl / key_task_permission (2)

4 views
Skip to first unread message

syzbot

unread,
Feb 18, 2024, 12:39:22 AMFeb 18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ced590523156 Merge tag 'driver-core-6.8-rc5' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16487044180000
kernel config: https://syzkaller.appspot.com/x/.config?x=35da3c2b3ebcd816
dashboard link: https://syzkaller.appspot.com/bug?extid=0acea935ab787b2a47b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [dhow...@redhat.com jar...@kernel.org jmo...@namei.org keyr...@vger.kernel.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org pa...@paul-moore.com se...@hallyn.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/05837f651734/disk-ced59052.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/580800f3c01b/vmlinux-ced59052.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6447e716fc3b/bzImage-ced59052.xz

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

==================================================================
BUG: KCSAN: data-race in __se_sys_keyctl / key_task_permission

write to 0xffff888141243270 of 4 bytes by task 29775 on cpu 0:
keyctl_setperm_key security/keys/keyctl.c:1097 [inline]
__do_sys_keyctl security/keys/keyctl.c:1925 [inline]
__se_sys_keyctl+0xab3/0xba0 security/keys/keyctl.c:1873
__x64_sys_keyctl+0x67/0x80 security/keys/keyctl.c:1873
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 0xffff888141243270 of 4 bytes by task 29757 on cpu 1:
key_task_permission+0x188/0x2b0 security/keys/permission.c:61
lookup_user_key+0x9e9/0xde0 security/keys/process_keys.c:803
keyctl_chown_key+0x112/0x5b0 security/keys/keyctl.c:970
__do_sys_keyctl security/keys/keyctl.c:1920 [inline]
__se_sys_keyctl+0x112/0xba0 security/keys/keyctl.c:1873
__x64_sys_keyctl+0x67/0x80 security/keys/keyctl.c:1873
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: 0x3f010000 -> 0x00000200

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 29757 Comm: syz-executor.4 Not tainted 6.8.0-rc4-syzkaller-00388-gced590523156 #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 24, 2024, 1:39:12 AMMar 24
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