KCSAN: data-race in assoc_array_apply_edit / search_nested_keyrings (4)

5 views
Skip to first unread message

syzbot

unread,
Apr 29, 2022, 7:46:20 AM4/29/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 259b897e5a79 Merge tag 'platform-drivers-x86-v5.18-3' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17fd026cf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a28b0f77655f4f1a
dashboard link: https://syzkaller.appspot.com/bug?extid=49f48ba13e8037689471
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [dhow...@redhat.com jar...@kernel.org jmo...@namei.org keyr...@vger.kernel.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org se...@hallyn.com]

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

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

==================================================================
BUG: KCSAN: data-race in assoc_array_apply_edit / search_nested_keyrings

write to 0xffff8881316c6190 of 8 bytes by task 9969 on cpu 1:
assoc_array_apply_edit+0x3c/0x650 lib/assoc_array.c:1356
__key_link+0x8a/0xc0 security/keys/keyring.c:1372
__key_instantiate_and_link+0x15b/0x290 security/keys/key.c:459
key_create_or_update+0x662/0x6f0 security/keys/key.c:941
__do_sys_add_key security/keys/keyctl.c:134 [inline]
__se_sys_add_key+0x280/0x310 security/keys/keyctl.c:74
__x64_sys_add_key+0x63/0x70 security/keys/keyctl.c:74
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff8881316c6190 of 8 bytes by task 9974 on cpu 0:
search_nested_keyrings+0x374/0xa50 security/keys/keyring.c:751
keyring_search_rcu+0xf4/0x180 security/keys/keyring.c:922
search_cred_keyrings_rcu+0x135/0x240 security/keys/process_keys.c:480
search_process_keyrings_rcu security/keys/process_keys.c:544 [inline]
lookup_user_key+0xaa7/0xd90 security/keys/process_keys.c:762
keyctl_read_key+0x29/0x390 security/keys/keyctl.c:834
__do_sys_keyctl security/keys/keyctl.c:1911 [inline]
__se_sys_keyctl+0x359/0x9e0 security/keys/keyctl.c:1869
__x64_sys_keyctl+0x63/0x70 security/keys/keyctl.c:1869
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0xffff888126d8b002 -> 0xffff888127b0cc02

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 9974 Comm: syz-executor.0 Not tainted 5.18.0-rc4-syzkaller-00083-g259b897e5a79-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


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

syzbot

unread,
Jun 2, 2022, 11:04:35 PM6/2/22
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