CVE-2026-53352 — signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 3.0≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < 90918794a4e2c3b440f8fcf3847765a8b1d81b25≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < dfcd0ba14769d94d76ac9d9814b85e7fcacd4e29≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < 8c046f36222c6ce1e0daef2c45c891c72602f8a1≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < 76aebd9ef20078719dfd6282d3b06c27e900a65a≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < f4aae11abb449dc536269705d0419ec69480faa9≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < f8d720bc2e35d568c18be0644e92a468de428370≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < 391ebe74456a0f1d60b3ba4a8a64d9f44c1728fe and 1 more≥ 39efa3ef3a376a4e53de2f82fc91182459d34200 and < 2b32b2fb241435145ea199efac024540759d2495 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 7.1-rc5version 7.1-rc6≥ 3.0 and < 5.10.259version 7.1-rc4version 7.1-rc3version 7.1-rc2version 7.1-rc1≥ 6.19 and < 7.0.13 and 5 more≥ 6.13 and < 6.18.36≥ 6.7 and < 6.12.94≥ 6.2 and < 6.6.143≥ 5.16 and < 6.1.176≥ 5.11 and < 5.15.210 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.7 | CVSS 3.1 | Medium | 1.0 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 4.7
- Source status changed · Published → Modified
- Record published
- Source status changed · → Published
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/391ebe74456a0f1d60b3ba4a8a64d9f44c1728fe
- git.kernel.org/stable/c/2b32b2fb241435145ea199efac024540759d2495
- git.kernel.org/stable/c/f8d720bc2e35d568c18be0644e92a468de428370
- git.kernel.org/stable/c/f4aae11abb449dc536269705d0419ec69480faa9
- git.kernel.org/stable/c/dfcd0ba14769d94d76ac9d9814b85e7fcacd4e29
- git.kernel.org/stable/c/90918794a4e2c3b440f8fcf3847765a8b1d81b25
- git.kernel.org/stable/c/8c046f36222c6ce1e0daef2c45c891c72602f8a1
- git.kernel.org/stable/c/76aebd9ef20078719dfd6282d3b06c27e900a65a
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 14h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 14h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53352 is "signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads()", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.