Linux kernel signal handling race condition in zap_other_threads
CVE-2026-53352Medium
When a multi-threaded process receives a stop signal and one thread calls execve(), the zap_other_threads() function fails to clear job control flags for the calling thread, leaving stale JOBCTL_STOP_PENDING flags. When the thread returns to user mode and checks for pending signals, it attempts to process the stale flag and decrements an already-zero counter, triggering a kernel warning. An attacker with the ability to run code in a multi-threaded process can trigger this race condition by calling execve() whilst the process receives a stop signal.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Detail
Affected versions
- linux linux kernel: from 3.0, before 5.10.259
- linux linux kernel: from 5.11, before 5.15.210
- linux linux kernel: from 5.16, before 6.1.176
- linux linux kernel: from 6.2, before 6.6.143
- linux linux kernel: from 6.7, before 6.12.94
- linux linux kernel: from 6.13, before 6.18.36
- linux linux kernel: from 6.19, before 7.0.13
- linux linux kernel: 7.1
Reports naming this CVE2 in total
· All CISA Advisories
Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (opens in a new tab)· All CISA Advisories
Siemens SIMATIC S7-1500 TM MFP (opens in a new tab)