From: syzbot <syzbot+75273239c9ffd7dc304f@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
wireguard@lists.zx2c4.com
Subject: [syzbot] [wireguard?] KCSAN: data-race in wg_packet_encrypt_worker / wg_packet_encrypt_worker
Date: Wed, 19 Aug 2026 05:07:37 -0700 [thread overview]
Message-ID: <6a859c89.f7a79266.2f965f.003e.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0f23d56f17fd Merge tag 'linux_kselftest-next-7.3-rc1' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11c9b679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e688dbf432017c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=75273239c9ffd7dc304f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a243b05cdc37/disk-0f23d56f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3af864b2bf56/vmlinux-0f23d56f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8c3f9cd19ac5/bzImage-0f23d56f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+75273239c9ffd7dc304f@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in wg_packet_encrypt_worker / wg_packet_encrypt_worker
read to 0xffff88811ac90080 of 4 bytes by task 3410 on cpu 0:
wg_cpumask_choose_online drivers/net/wireguard/queueing.h:107 [inline]
wg_queue_enqueue_per_peer_tx drivers/net/wireguard/queueing.h:183 [inline]
wg_packet_encrypt_worker+0x9f5/0xe90 drivers/net/wireguard/send.c:305
process_one_work kernel/workqueue.c:3322 [inline]
process_scheduled_works+0x4d4/0x9a0 kernel/workqueue.c:3405
worker_thread+0x569/0x750 kernel/workqueue.c:3486
kthread+0x221/0x270 kernel/kthread.c:436
ret_from_fork+0x146/0x330 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
write to 0xffff88811ac90080 of 4 bytes by task 15243 on cpu 1:
wg_cpumask_choose_online drivers/net/wireguard/queueing.h:110 [inline]
wg_queue_enqueue_per_peer_tx drivers/net/wireguard/queueing.h:183 [inline]
wg_packet_encrypt_worker+0xcca/0xe90 drivers/net/wireguard/send.c:305
process_one_work kernel/workqueue.c:3322 [inline]
process_scheduled_works+0x4d4/0x9a0 kernel/workqueue.c:3405
worker_thread+0x569/0x750 kernel/workqueue.c:3486
kthread+0x221/0x270 kernel/kthread.c:436
ret_from_fork+0x146/0x330 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
value changed: 0x00000002 -> 0x00000000
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 15243 Comm: kworker/1:19 Tainted: G W syzkaller #0 PREEMPT(lazy)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: wg-crypt-wg0 wg_packet_encrypt_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 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:[~2026-08-19 12:07 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=6a859c89.f7a79266.2f965f.003e.GAE@google.com \
--to=syzbot+75273239c9ffd7dc304f@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wireguard@lists.zx2c4.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