[moderation] [serial?] KCSAN: data-race in __stop_tty / do_con_write (11)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 551c722f4080 Merge tag 'rtc-7.3-fixes' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=163d2b15580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea1e6d8de13bab08
dashboard link: https://syzkaller.appspot.com/bug?extid=307a5204e7c9c75f6eea
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
CC: [gre...@linuxfoundation.org jiri...@kernel.org 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/a6b05bccc40f/disk-551c722f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5a247a4f5187/vmlinux-551c722f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5a6d70478180/bzImage-551c722f.xz

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

==================================================================
BUG: KCSAN: data-race in __stop_tty / do_con_write

write to 0xffff88811c014594 of 1 bytes by task 5819 on cpu 0:
__stop_tty+0x36/0x90 drivers/tty/tty_io.c:744
n_tty_ioctl_helper+0x2d1/0x370 drivers/tty/tty_ioctl.c:951
n_tty_ioctl+0x101/0x200 drivers/tty/n_tty.c:2496
tty_ioctl+0x83e/0xb80 drivers/tty/tty_io.c:2774
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xce/0x140 fs/ioctl.c:583
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:583
x64_sys_call+0x239d/0x2550 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x112/0x360 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88811c014594 of 1 bytes by task 5821 on cpu 1:
do_con_write+0x1bd5/0x2a90 drivers/tty/vt/vt.c:3305
con_write+0x27/0x1d0 drivers/tty/vt/vt.c:3661
process_output_block drivers/tty/n_tty.c:557 [inline]
n_tty_write+0x7f4/0xb00 drivers/tty/n_tty.c:2366
iterate_tty_write drivers/tty/tty_io.c:1006 [inline]
file_tty_write+0x392/0x6a0 drivers/tty/tty_io.c:1054
tty_write+0x25/0x30 drivers/tty/tty_io.c:1075
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x57f/0x9a0 fs/read_write.c:687
ksys_write+0xdc/0x1a0 fs/read_write.c:739
__do_sys_write fs/read_write.c:750 [inline]
__se_sys_write fs/read_write.c:747 [inline]
__x64_sys_write+0x40/0x50 fs/read_write.c:747
x64_sys_call+0x154e/0x2550 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x112/0x360 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 5821 Comm: syz.2.653 Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
==================================================================


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