[moderation] [wireguard?] KCSAN: data-race in wg_index_hashtable_insert / wg_index_hashtable_lookup (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cf1182944c7c Merge tag 'lsm-pr-20240227' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1744034a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=53006d590acdf777
dashboard link: https://syzkaller.appspot.com/bug?extid=d60084d607260679e92b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [Ja...@zx2c4.com da...@davemloft.net edum...@google.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pab...@redhat.com wire...@lists.zx2c4.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d97150d7df11/disk-cf118294.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8a0471d6aa24/vmlinux-cf118294.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1fa472868049/bzImage-cf118294.xz

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

==================================================================
BUG: KCSAN: data-race in wg_index_hashtable_insert / wg_index_hashtable_lookup

write to 0xffff88813943cfdc of 4 bytes by task 3175 on cpu 1:
wg_index_hashtable_insert+0xe2/0x2a0 drivers/net/wireguard/peerlookup.c:132
wg_noise_handshake_create_response+0x529/0x5d0 drivers/net/wireguard/noise.c:713
wg_packet_send_handshake_response+0x6e/0x120 drivers/net/wireguard/send.c:94
wg_receive_handshake_packet drivers/net/wireguard/receive.c:154 [inline]
wg_packet_handshake_receive_worker+0x3ed/0x5e0 drivers/net/wireguard/receive.c:213
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:243

read to 0xffff88813943cfdc of 4 bytes by task 8 on cpu 0:
wg_index_hashtable_lookup+0x5b/0x120 drivers/net/wireguard/peerlookup.c:211
wg_noise_handshake_consume_response+0x12c/0x710 drivers/net/wireguard/noise.c:747
wg_receive_handshake_packet drivers/net/wireguard/receive.c:166 [inline]
wg_packet_handshake_receive_worker+0x3fb/0x5e0 drivers/net/wireguard/receive.c:213
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:243

value changed: 0xa7f8bf93 -> 0x7556e9e5

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.8.0-rc6-syzkaller-00021-gcf1182944c7c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: wg-kex-wg1 wg_packet_handshake_receive_worker
==================================================================


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