CVE-2026-53352

In the Linux kernel, the following vulnerability has been resolved: signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads() When a multi-threaded process receives a stop signal (e.g., SIGSTOP), do_signal_stop() sets JOBCTL_STOP_PENDING and JOBCTL_STOP_CONSUME on all threads and sets signal->group_stop_count to the number of threads. If one of the threads concurrently calls execve(), de_thread() invokes zap_other_threads() to kill all other threads. zap_other_threads() aborts the pending group stop by resetting signal->group_stop_count to 0 and clears the JOBCTL_PENDING_MASK for all other threads. However, it fails to clear the job control flags for the calling thread. When execve() completes, the calling thread returns to user mode and checks for pending signals. Seeing the stale JOBCTL_STOP_PENDING flag, it calls do_signal_stop(), which invokes task_participate_group_stop(). Since JOBCTL_STOP_CONSUME is still set, it attempts to decrement the already-zero signal->group_stop_count, triggering a warning: sig->group_stop_count == 0 WARNING: CPU: 1 PID: 6475 at kernel/signal.c:373 task_participate_group_stop+0x215/0x2d0 Call Trace: <TASK> do_signal_stop+0x3be/0x5c0 kernel/signal.c:2619 get_signal+0xa8c/0x1330 kernel/signal.c:2884 arch_do_signal_or_restart+0xbc/0x840 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop+0x8c/0x4d0 kernel/entry/common.c:98 do_syscall_64+0x33e/0xf80 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> Fix this race condition by clearing the JOBCTL_PENDING_MASK for the calling thread in zap_other_threads(), ensuring it does not retain any stale job control state after the thread group is destroyed. This aligns with other functions that tear down a thread group and abort group stops, such as zap_process() and complete_signal(), which correctly clear these flags for all threads including the current one.

• CWE-362

• https://git.kernel.org/stable/c/2b32b2fb241435145ea199efac024540759d2495Patch
• https://git.kernel.org/stable/c/391ebe74456a0f1d60b3ba4a8a64d9f44c1728fePatch
• https://git.kernel.org/stable/c/76aebd9ef20078719dfd6282d3b06c27e900a65aPatch
• https://git.kernel.org/stable/c/8c046f36222c6ce1e0daef2c45c891c72602f8a1Patch
• https://git.kernel.org/stable/c/90918794a4e2c3b440f8fcf3847765a8b1d81b25Patch
• https://git.kernel.org/stable/c/dfcd0ba14769d94d76ac9d9814b85e7fcacd4e29Patch
• https://git.kernel.org/stable/c/f4aae11abb449dc536269705d0419ec69480faa9Patch
• https://git.kernel.org/stable/c/f8d720bc2e35d568c18be0644e92a468de428370Patch

Published

Jul 1, 2026

Last Modified

Jul 22, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-53347In the Linux kernel, the following vulnerability has been re…
• CVE-2026-53348In the Linux kernel, the following vulnerability has been re…
• CVE-2026-53349In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-5335The Magic Export & Import WordPress plugin before 1.2.0 stor…5.3
• CVE-2026-53350In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53351In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53353In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53354In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-53355In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-53356In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-53357In the Linux kernel, the following vulnerability has been re…8
• CVE-2026-53358In the Linux kernel, the following vulnerability has been re…8.8