[moderation] [serial?] KCSAN: data-race in serial8250_do_startup / serial8250_handle_irq_locked

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bfe62a454542 Merge tag 'soc-fixes-7.0-2' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=147a134e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3a78dd265deac3a9
dashboard link: https://syzkaller.appspot.com/bug?extid=258f8f37475c9fa49dc6
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.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/fc39db873abf/disk-bfe62a45.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ab283b708df/vmlinux-bfe62a45.xz
kernel image: https://storage.googleapis.com/syzbot-assets/69cef2875afd/bzImage-bfe62a45.xz

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

==================================================================
BUG: KCSAN: data-race in serial8250_do_startup / serial8250_handle_irq_locked

write to 0xffffffff893ff4c6 of 1 bytes by task 26348 on cpu 1:
serial8250_do_startup+0x1628/0x1d50 drivers/tty/serial/8250/8250_port.c:2334
serial8250_startup+0x41/0x50 drivers/tty/serial/8250/8250_port.c:2354
uart_port_startup drivers/tty/serial/serial_core.c:321 [inline]
uart_startup+0x464/0xae0 drivers/tty/serial/serial_core.c:365
uart_port_activate+0x67/0xc0 drivers/tty/serial/serial_core.c:1949
tty_port_open+0x196/0x270 drivers/tty/tty_port.c:747
uart_open+0x30/0x40 drivers/tty/serial/serial_core.c:1929
tty_open+0x3d4/0xaf0 drivers/tty/tty_io.c:2137
chrdev_open+0x2eb/0x3a0 fs/char_dev.c:411
do_dentry_open+0x4ca/0xa90 fs/open.c:949
vfs_open+0x37/0x1e0 fs/open.c:1081
do_open fs/namei.c:4677 [inline]
path_openat+0x1b70/0x2050 fs/namei.c:4836
do_file_open+0x16c/0x290 fs/namei.c:4865
do_sys_openat2+0x94/0x130 fs/open.c:1366
do_sys_open fs/open.c:1372 [inline]
__do_sys_openat fs/open.c:1388 [inline]
__se_sys_openat fs/open.c:1383 [inline]
__x64_sys_openat+0xf2/0x120 fs/open.c:1383
x64_sys_call+0x1e39/0x3020 arch/x86/include/generated/asm/syscalls_64.h:258
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x12c/0x370 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffffffff893ff4c6 of 1 bytes by interrupt on cpu 0:
serial8250_handle_irq_locked+0x354/0x420 drivers/tty/serial/8250/8250_port.c:1823
serial8250_handle_irq+0xad/0x280 drivers/tty/serial/8250/8250_port.c:1841
serial8250_default_handle_irq+0x8e/0x170 drivers/tty/serial/8250/8250_port.c:1855
serial8250_interrupt+0x63/0x130 drivers/tty/serial/8250/8250_core.c:86
__handle_irq_event_percpu+0x9c/0x4d0 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+0x154/0x470 kernel/irq/chip.c:855
generic_handle_irq_desc include/linux/irqdesc.h:186 [inline]
handle_irq arch/x86/kernel/irq.c:262 [inline]
call_irq_handler arch/x86/kernel/irq.c:-1 [inline]
__common_interrupt+0x60/0xb0 arch/x86/kernel/irq.c:333
common_interrupt+0x3e/0x90 arch/x86/kernel/irq.c:326
asm_common_interrupt+0x26/0x40 arch/x86/include/asm/idtentry.h:688

value changed: 0x00 -> 0x05

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 23268 Comm: syz-executor Tainted: G W syzkaller #0 PREEMPT(full)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/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