Hello,
syzbot found the following issue on:
HEAD commit: 48a5a7ab8d6a Merge tag 'v7.2-rc4-smb3-client-fixes' of git..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1400c7b1580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=84b3039e8461eef5
dashboard link:
https://syzkaller.appspot.com/bug?extid=96605ccb04166cb6cfe8
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
CC: [
dmitry....@gmail.com linux...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/f80e802da100/disk-48a5a7ab.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/c52d5cfe5b19/vmlinux-48a5a7ab.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/117a746cd695/bzImage-48a5a7ab.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+96605c...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in ps2_do_sendbyte / ps2_interrupt
write to 0xffff888103b3ea48 of 8 bytes by interrupt on cpu 0:
ps2_interrupt+0x50d/0x550 drivers/input/serio/libps2.c:-1
serio_interrupt+0x66/0xf0 drivers/input/serio/serio.c:967
i8042_handle_data+0x388/0x680 drivers/input/serio/i8042.c:598
i8042_interrupt+0x15/0x90 drivers/input/serio/i8042.c:605
__handle_irq_event_percpu+0x8b/0x480 kernel/irq/handle.c:209
handle_irq_event_percpu kernel/irq/handle.c:246 [inline]
handle_irq_event+0x64/0xf0 kernel/irq/handle.c:263
handle_edge_irq+0x155/0x440 kernel/irq/chip.c:859
generic_handle_irq_desc include/linux/irqdesc.h:188 [inline]
handle_irq arch/x86/kernel/irq.c:209 [inline]
call_irq_handler arch/x86/kernel/irq.c:-1 [inline]
__common_interrupt+0x60/0xb0 arch/x86/kernel/irq.c:280
common_interrupt+0x7e/0x90 arch/x86/kernel/irq.c:273
asm_common_interrupt+0x26/0x40 arch/x86/include/asm/idtentry.h:665
check_kcov_mode kernel/kcov.c:183 [inline]
__sanitizer_cov_trace_pc+0x30/0x70 kernel/kcov.c:217
get_next_corpse net/netfilter/nf_conntrack_core.c:2315 [inline]
nf_ct_iterate_cleanup+0x1c4/0x3c0 net/netfilter/nf_conntrack_core.c:2366
nf_ct_iterate_cleanup_net+0x8c/0xb0 net/netfilter/nf_conntrack_core.c:2387
iterate_cleanup_work+0x7b/0x170 net/netfilter/nf_nat_masquerade.c:87
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
read to 0xffff888103b3ea48 of 8 bytes by task 9550 on cpu 1:
ps2_do_sendbyte+0x17e/0x320 drivers/input/serio/libps2.c:65
__ps2_command+0x3b7/0xaa0 drivers/input/serio/libps2.c:328
ps2_command+0x52/0x90 drivers/input/serio/libps2.c:403
synaptics_detect+0x5e/0x130 drivers/input/mouse/synaptics.c:102
psmouse_do_detect drivers/input/mouse/psmouse-base.c:987 [inline]
psmouse_extensions+0x4df/0x960 drivers/input/mouse/psmouse-base.c:1082
__psmouse_reconnect+0x3da/0x8b0 drivers/input/mouse/psmouse-base.c:1685
psmouse_reconnect+0x17/0x20 drivers/input/mouse/psmouse-base.c:1723
serio_reconnect_driver drivers/input/serio/serio.c:52 [inline]
serio_reconnect_port drivers/input/serio/serio.c:558 [inline]
serio_handle_event+0x1c7/0xac0 drivers/input/serio/serio.c:201
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: 0x0000000000000001 -> 0x0000000000000000
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 9550 Comm: kworker/1:2 Tainted: G W syzkaller #0 PREEMPT(lazy)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Workqueue: events_long serio_handle_event
==================================================================
---
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