[syzbot] [kernel?] KCSAN: data-race in 0x0 / fpu_flush_thread

From: syzbot

Date: Wed Nov 18 2026 - 22:42:32 EST


Hello,

syzbot found the following issue on:

HEAD commit: 666539eecdf4 Merge tag 'assoc-array-fixes-v2'
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1624fad9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b949a9d3c1d44ceb
dashboard link: https://syzkaller.appspot.com/bug?extid=58cbd7974a103b8b8916
compiler: Debian clang version 22.1.8 (1~deb13u4), 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/a943b9915869/disk-666539ee.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9bfd839d7ea5/vmlinux-666539ee.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0f20b9720a71/bzImage-666539ee.xz

AI-generated root cause summary:
In fpu_flush_thread() (invoked during execve via flush_thread()),
fpstate_reset() modifies the task's fpu->fpstate pointer and resets fpstate
configuration fields without holding fpregs_lock() and before the live hardware
FPU registers are invalidated. If preemption or a softirq occurs during
fpstate_reset(), switch_fpu() executes save_fpregs_to_fpstate(), which
concurrently reads fpstate->xfeatures and writes hardware register state into
fpu->fpstate. When dynamic features such as AMX are active, saving live
registers into the newly assigned default fixed fpstate buffer triggers an
out-of-bounds memory write.

full analysis: https://syzkaller.appspot.com/x/ai_root_cause?x=58cbd7974a103b8b8916

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+58cbd7974a103b8b8916@xxxxxxxxxxxxxxxxxxxxxxxxx

==================================================================
BUG: KCSAN: data-race in 0x0 / fpu_flush_thread

read to 0xffff888104809f18 of 8 bytes by task 10978 on cpu 0:

write to 0xffff888104809f18 of 8 bytes by task 10978 on cpu 0:
__fpstate_reset arch/x86/kernel/fpu/core.c:-1 [inline]
fpstate_reset arch/x86/kernel/fpu/core.c:620 [inline]
fpu_flush_thread+0x128/0x360 arch/x86/kernel/fpu/core.c:882
flush_thread+0x40/0x80 arch/x86/kernel/process.c:291
begin_new_exec+0xcd0/0x1260 fs/exec.c:1235
load_elf_binary+0x5ee/0x1a00 fs/binfmt_elf.c:1010
search_binary_handler fs/exec.c:1777 [inline]
exec_binprm fs/exec.c:1809 [inline]
bprm_execve+0x480/0xaa0 fs/exec.c:1865
do_execveat_common+0x6ba/0x720 fs/exec.c:1963
__do_sys_execve fs/exec.c:2036 [inline]
__se_sys_execve fs/exec.c:2030 [inline]
__x64_sys_execve+0x5f/0x80 fs/exec.c:2030
x64_sys_call+0x1cd2/0x2550 arch/x86/include/generated/asm/syscalls_64.h:60
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 10978 Comm: dhcpcd-run-hook Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/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 syzkaller@xxxxxxxxxxxxxxxx.

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