Description
In the Linux kernel, the following vulnerability has been resolved:

entry: Fix seccomp bypass after ptrace with TSYNC

Sashiko review pointed out the following issue.

If a thread is stopped in syscall_trace_enter() for ptrace, another
thread can install a seccomp filter with SECCOMP_FILTER_FLAG_TSYNC
(e.g., via seccomp_attach_filter()). This will successfully set
SYSCALL_WORK_SECCOMP on the stopped thread, but syscall_trace_enter()
evaluates a cached 'work' variable sampled on entry. Consequently,
the subsequent check for SYSCALL_WORK_SECCOMP misses the newly
assigned flag, and the filter is silently bypassed.

This race condition could allow an unprivileged process to execute
a prohibited system call (e.g., execve) that the newly installed filter
was intended to block, especially since the tracer might have modified
the system call number during the ptrace stop.

Fix this by re-reading the syscall_work flags after ptrace handling,
so that any new SYSCALL_WORK_SECCOMP flag set by another thread via
TSYNC during the ptrace stop is observed before the subsequent
seccomp check.
Published: 2026-09-11
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Bypass of seccomp filters allowing unauthorized system calls
Action: Apply Patch
AI Analysis

Impact

A race condition in the Linux kernel enables a thread halted in the ptrace stop to miss a newly installed seccomp filter. When a second thread attaches a TSYNC‑enabled filter during the stop, the original thread reads a stale flag, causing the seccomp check to be omitted. The flaw permits execution of system calls that a properly installed filter would block, such as execve. This issue is a classic concurrency weakness, reflected in CWE‑362 and CWE‑367.

Affected Systems

All Linux kernel releases prior to the commit that re‑reads syscall_work flags after ptrace handling are affected. The vulnerability is listed for the generic Linux kernel product; no specific kernel versions are enumerated, so any build released before the patch remains at risk.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity, while the EPSS score of <1% indicates a low probability of exploitation, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector, based on the description, requires a process with ptrace privileges that can stop a target thread while concurrently another thread installs a TSYNC‑enabled seccomp filter. If ptrace usage is restricted on a system, the opportunity for exploitation diminishes significantly. For systems that allow broad ptrace access, the race flaw could be exploited by an unprivileged user to execute prohibited system calls.

Generated by OpenCVE AI on September 12, 2026 at 17:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the patch re‑reading syscall_work flags after ptrace handling
  • Limit the use of ptrace by configuring ptrace_scope, disabling CAP_SYS_PTRACE for untrusted users, or applying a security module that restricts ptrace
  • Disable or restrict SECCOMP_FILTER usage, especially with SECCOMP_FILTER_FLAG_TSYNC, on systems where it is not needed

Generated by OpenCVE AI on September 12, 2026 at 17:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 12 Sep 2026 17:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Sat, 12 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}

threat_severity

Moderate


Sat, 12 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: entry: Fix seccomp bypass after ptrace with TSYNC Sashiko review pointed out the following issue. If a thread is stopped in syscall_trace_enter() for ptrace, another thread can install a seccomp filter with SECCOMP_FILTER_FLAG_TSYNC (e.g., via seccomp_attach_filter()). This will successfully set SYSCALL_WORK_SECCOMP on the stopped thread, but syscall_trace_enter() evaluates a cached 'work' variable sampled on entry. Consequently, the subsequent check for SYSCALL_WORK_SECCOMP misses the newly assigned flag, and the filter is silently bypassed. This race condition could allow an unprivileged process to execute a prohibited system call (e.g., execve) that the newly installed filter was intended to block, especially since the tracer might have modified the system call number during the ptrace stop. Fix this by re-reading the syscall_work flags after ptrace handling, so that any new SYSCALL_WORK_SECCOMP flag set by another thread via TSYNC during the ptrace stop is observed before the subsequent seccomp check.
Title entry: Fix seccomp bypass after ptrace with TSYNC
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-11T19:45:06.613Z

Reserved: 2026-09-11T19:38:34.732Z

Link: CVE-2026-89603

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:19:45.243

Modified: 2026-09-11T20:19:45.243

Link: CVE-2026-89603

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:45:06Z

Links: CVE-2026-89603 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-12T17:30:16Z

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition