Hello,
syzbot found the following issue on:
HEAD commit: 4405c18c95d2 Merge tag 'mm-nonmm-hotfixes-stable-2026-11-1..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1667e2b5580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=886d2ddd2d6b664e
dashboard link:
https://syzkaller.appspot.com/bug?extid=3c7d70c3bcdea393cc30
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
CC: [
linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/bc2915167a4c/disk-4405c18c.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/cdf4152506d9/vmlinux-4405c18c.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/04690243718a/bzImage-4405c18c.xz
AI-generated root cause summary:
A KCSAN data race occurs on `task_struct::flags` between a thread setting
`PF_SIGNALED` in `get_signal()` (`current->flags |= PF_SIGNALED` after dropping
`sighand->siglock`) and an exiting sibling thread checking `!(t->flags &
PF_EXITING)` in `find_alive_thread()` while holding `tasklist_lock`. Neither
side uses `READ_ONCE()`/`WRITE_ONCE()` or shares a common lock for `t->flags`
updates outside `exit_signals()`, allowing concurrent unmarked 4-byte accesses
to the same `unsigned int flags` field. The race is benign in practice because
`current` is the sole writer to `t->flags` and `tasklist_lock` serializes
`exit_notify()`.
full analysis:
https://syzkaller.appspot.com/x/ai_root_cause?x=3c7d70c3bcdea393cc30
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3c7d70...@syzkaller.appspotmail.com
loop5: detected capacity change from 0 to 33792
EXT4-fs: Ignoring removed bh option
EXT4-fs (loop5): can't mount with data_err=abort, fs mounted w/o journal
==================================================================
BUG: KCSAN: data-race in do_exit / get_signal
read-write to 0xffff888101df22ac of 4 bytes by task 7741 on cpu 0:
get_signal+0xac5/0xd30 kernel/signal.c:3084
arch_do_signal_or_restart+0x96/0x480 arch/x86/kernel/signal.c:337
__exit_to_user_mode_loop kernel/entry/common.c:66 [inline]
exit_to_user_mode_loop+0x161/0x940 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:343 [inline]
do_syscall_64+0x23b/0x3a0 arch/x86/entry/syscall_64.c:107
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff888101df22ac of 4 bytes by task 7739 on cpu 1:
find_alive_thread kernel/exit.c:596 [inline]
find_new_reaper kernel/exit.c:646 [inline]
forget_original_parent kernel/exit.c:716 [inline]
exit_notify kernel/exit.c:749 [inline]
do_exit+0x5b6/0x1530 kernel/exit.c:992
do_group_exit+0xfe/0x140 kernel/exit.c:1123
get_signal+0xc49/0xd30 kernel/signal.c:3113
arch_do_signal_or_restart+0x96/0x480 arch/x86/kernel/signal.c:337
__exit_to_user_mode_loop kernel/entry/common.c:66 [inline]
exit_to_user_mode_loop+0x161/0x940 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:343 [inline]
do_syscall_64+0x23b/0x3a0 arch/x86/entry/syscall_64.c:107
entry_SYSCALL_64_after_hwframe+0x77/0x7f
value changed: 0x00400140 -> 0x0040054c
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 7739 Comm: syz.5.918 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
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