Menu

Star on GitHub · 3.2k

CVE-2026-53352

4.7 · MEDIUM

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.,…

Published Jul 1, 2026CWE-362EPSS 0.10%

Overview

CVE-2026-53352 is a medium-severity vulnerability. It was published on July 1, 2026 and has a CVSS 3.1 base score of 4.7 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-53352?

CVE-2026-53352 is a medium-severity vulnerability. It was published on July 1, 2026 and has a CVSS 3.1 base score of 4.7 (MEDIUM).

How severe is CVE-2026-53352?

This vulnerability has a CVSS 3.1 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53352?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53352?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53352 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all